Digital downloading jukebox system with user-tailored music management, communications, and other tools

ABSTRACT

A digital downloading jukebox system including a mechanism for delivering custom services to a recognized user, including services for creating playlists, communicating with others, accessing other features, etc. is provided. In some exemplary embodiments, after a user is recognized, the jukebox system allows users to access a special front-end via an Internet-enabled device or on an actual jukebox. Then, the user may, for example, create playlists, share songs with friends, send messages to friends, and access other value-added content. Such a system preferably learns about networks of friends, and enables managers to send similar messages to regular customers and/or others known to the system. In some exemplary embodiments, changes via a first user interface on a first device are reflected on second user interface on other properly-configured devices.

CROSS-REFERENCES TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.14/555,861 filed Nov. 28, 2014, which is a continuation of U.S. patentapplication Ser. No. 14/222,895 filed Mar. 24, 2014, now U.S. Pat. No.8,918,485, which is a divisional of U.S. patent application Ser. No.13/673,086 filed Nov. 9, 2012, now U.S. Pat. No. 8,719,873, which is acontinuation of U.S. patent application Ser. No. 11/358,721 filed Feb.22, 2006, now U.S. Pat. No. 8,332,895, which is a continuation-in-partof U.S. patent application Ser. No. 11/222,036 filed Sep. 9, 2005, nowU.S. Pat. No. 8,151,304, which is a continuation-in-part of U.S. patentapplication Ser. No. 11/185,974 filed Jul. 21, 2005, now U.S. Pat. No.8,103,589, which is a continuation-in-part of U.S. patent applicationSer. No. 10/661,811 filed Sep. 15, 2003, pending, which claims thebenefit of U.S. Provisional Patent Application No. 60/410,832 filed Sep.16, 2002, the entire contents of each of which are hereby incorporatedby reference in this application.

FIELD

The instant invention relates to, for example, jukebox systems and, moreparticularly, to digital downloading jukebox systems of the type whichtypically include a central server and remote jukebox devices thatcommunicate with the central server for royalty accounting and/orcontent updates and, still more particularly, to jukebox systems thatprovide user-tailored music management, communications, and other toolsfor recognized users using the jukebox system. Exemplary embodiments ofthe instant invention improve such systems by providing a local serverfor each jukebox device in the jukebox system network. The local serverprovides a second and more expansive source of content (e.g., audioand/or visual data) that can be selected by a user of the jukebox devicefor reproduction on the jukebox device. The local servers may provide amirror of or subset of the central server, thereby enabling the entirelibrary of audio and/or visual data, or at least the most requestedcontent, to be conveniently available to each jukebox device without theneed to download requested content, that is not available on the massstorage device of the jukebox device itself, from the central server.The collective group of local servers may also act as a network ofdistributed content servers that can be controlled by the central serverthrough each jukebox device to provide services to other devices, suchas, for example, other jukebox devices. In addition, the jukebox deviceand local server can, under control of the central server, operate as a“central hub” or management device for various downloadable fee-baseddevices present in a location with the jukebox device.

Exemplary embodiments additionally can provide other mechanisms toenhance individual recognized users' experiences, such as, for example,by allowing users to create and manage playlists that can be retrievedon one or more jukeboxes, create and manage buddy lists that can sendmessages to individuals or broadcast to large groups of individuals,etc. In other words, in one embodiment, the jukebox includes featureswhich enable the jukebox to recognize specific jukebox users, throughprior registration or the like, and to provide user-specific services tothe user. For example, the jukebox may allow the recognized user tocreate, edit and/or store custom playlists on the jukebox that can beselected by the user or other registered users designated by the creatorof the playlist for play on the jukebox. The jukebox may also allowregistered users to communicate with other registered users through thejukebox. Registered users may also be provided with credit on thejukebox so that cash is not necessary for using the jukebox services.The jukebox may also be used to provide background music services inaddition to conventional jukebox services in a unique and advantageousmanner as described herein. The jukebox may additionally increase asense of ownership by interacting with a interactive applicationaccessible at a location remote from the jukebox, such as, for example,via the Internet. The remote application may connect individuals to anonline community through which users can, for example, communicate withother users, build playlists, share playlists, suggest music to others,participate in promotions, link to targeted advertisements, etc.Additionally, the jukebox and/or remote application may allow users todownload information to a portable device, such as, for example, a cellphone, a personal digital assistant, an MP3 player, etc.

BACKGROUND AND SUMMARY

Jukeboxes have been around for decades and provide users with theability to select desired music for reproduction in a convenient andadvantageous manner. Jukeboxes have conventionally been provided incommercial establishments, such as restaurants and bars, in order toprovide desired music on demand for patrons thereof for a fee. Over thelast several years, a new generation of jukebox devices have becomeavailable that provide significant improvements in the operation thereoffor all parties involved. More specifically, the conventional standalonephonorecord and CD jukeboxes are being replaced by digital downloadingjukeboxes that are controlled by and communicate with a central server.An example of this new generation jukebox system is shown in U.S. Pat.No. 6,308,204, the entire disclosure of which is incorporated herein byreference. A leading provider of this new generation of jukebox systemsis TouchTunes Music Corporation.

FIG. 1 shows an overview of an exemplary embodiment of a digitaldownloading jukebox system 10 (hereinafter referred to simply as a“jukebox system”). As shown in FIG. 1, the jukebox system 10 includes acentral server 12 that contains a master library of audio content(typically music), as well as or alternatively audiovisual content(typically music and associated video or graphics), that can bedownloaded therefrom. The jukebox system also includes a series ofremote jukebox devices 16, 16 a-16 f. Each of these jukebox devices aregenerally located in a bar, restaurant, club or other desired location,and are operable to play music in response to receiving a payment from auser, such as coins, bills, credit/debit card, etc., and having one ormore songs selected by the user for play. In an alternative embodiment,a music service is paid for on a subscription basis by the location, andthe selected music is free for the end-user. The jukebox device 16typically includes a screen 18 that presents information to the user andallows the user to select songs therefrom, as well as an audio system 20that plays the selected songs. The screen 18 may also be used fordisplaying song-related video or graphics. The screen 18 may also beused to display advertisements for the jukebox itself in order toattract customers thereto, to display other types of advertisements,and/or to display any other desired information.

The jukebox devices 16 (sometimes referred to as simply “jukeboxes”herein) are operable to communicate with the central server 12 through acommunications network 14, such as, for example, the Internet. Thejukeboxes 16 periodically communicate with the server 12 in order toprovide information to the server 12 regarding the specific songs thathave been played on the jukebox. The central server then uses thisinformation in order to determine the appropriate royalties and/or otherpayments that are owed for songs played on each jukebox. Thus, onesignificant advantage of this new generation of jukeboxes is that thesound reproduction and/or other applicable music rights can be adheredto in a more accurate and reliable manner, thereby assuring the properroyalties are paid to the artists or music owners. The central server 12can also provide new songs to the jukebox 16 in order to assure that theappropriate or most popular songs are maintained on the jukebox based onthe specific customers at that location. Thus, the songs available oneach jukebox can be customized through communication with the centralserver in order to provide the songs and/or types of music thatcustomers generally request at each jukebox location. As described inthe above-referenced U.S. Pat. No. 6,308,204, the central server canalso advantageously be used to update the operating software on thejukeboxes in order to, for example, change the operation of the jukebox,such as to provide new or improved features. Thus, another significantadvantage of this new generation of jukeboxes is that the songs (orother audio and/or visual content), and the operation of the jukeboxitself can be remotely changed as desired without the need to havesomeone (such as a routeman) personally service the jukebox. Instead,such updates can be done using the central server 12.

As indicated above, the jukebox devices 16 each include a mass storagedevice, such as a hard drive, which stores the songs and associatedvideo/graphics data (if any), as well as any other desired graphicalinformation for reproduction on the jukebox. The mass storage device ofthe jukebox typically has limited storage capacity relative to thestorage device of the central server 12. As a result, only a fraction ofthe songs stored on the central server are typically stored on the massstorage device of the jukebox at any one time. There may be otherreasons as well, such as for security of the data or limited room in thejukebox itself, for having limited storage capacity on the jukeboxand/or limiting the number of songs stored thereon. For example,physical space may be limited on wall-mount jukeboxes or the like, whichare designed to be small in size as compared to free-standing models. Asexplained above, the songs on the jukebox can be changed throughcommunication with the central server, but typically any one jukeboxonly stores a relatively small subset of the complete library of songsmaintained by the central server at any one time.

In order to maximize the revenue that a jukebox generates, it isimportant to make the most desired songs available on the jukebox overtime. If customers cannot find songs they like on the jukebox, usage ofthe jukebox (and the revenue generated thereby) will dramaticallydecrease. On the other hand, it is impossible to predict in advanceexactly what a customer at any particular location will desire to playon the jukebox. In fact, there are likely many instances where acustomer would have selected a song that exists on the central serverbut is not currently present on the jukebox. As a result, the jukeboxmay not be enjoyed and used to its fullest extent. In order to addressthis problem and increase revenue, jukebox systems have in the pastprovided a feature which enables the user to search for songs on thecentral server from the jukebox and request an immediate download of adesired song from the central server to the jukebox for an additionalfee. This feature enables the user to play any song in the masterlibrary of songs maintained by the central server using the jukebox,regardless of whether or not the specific song is presently stored inthe mass storage of the jukebox itself. Thus, the user can first lookfor desired songs on the local storage of the jukebox and then, ifdesired, search further on the central server for desired songs. Thejukebox device typically charges an additional fee (such as five creditsinstead on one credit) for an immediate download and play of a song fromthe central server as opposed to a standard play directly from thejukebox's local storage.

One problem, however, with the immediate downloading feature is that itis desirable to have an immediate and high speed connection with thecentral server to implement. In addition, the central server and networkmust be prepared for and capable of handling such requests in a reliableand efficient manner for the feature to properly operate. Theserequirements cannot always be met and, as a result, implementation ofthis feature has been limited. For example, many locations that havejukeboxes do not have high speed connections (such as DSL) and insteaduse dial-up modem connections. Jukeboxes which rely on dial-upconnections generally are only designed to communicate with the serverperiodically and do not allow the user to immediately download a song.They have, however, enabled a user to vote for a song to be downloadedat a later time when the dial-up connection is made. This, of course, isnot as satisfying to the user as being able to immediately download asong. Other problems can arise in connection with this download featureif the network or server is not currently available for the download,due to traffic, malfunctions or the like.

For most users, a relationship with a jukebox extends only as far as achoice of songs to play. Casual users may find it difficult to makeselections rapidly and/or to locate specific songs. Regular users,however, frequently choose the same songs, and they may becomefrustrated with always having to make the same selections. Both problemsmay result in a loss of revenue from intimidation, frustration, etc.

Thus, it is a feature of the exemplary embodiments to create arelationship between the jukebox and the patrons, in view of the furtherfeature of creating a relationship with a whole community of jukeboxusers. Such a system can establish a trust relationship between thejukebox and the patrons, while also creating a sense of ownership forthe patrons by allowing them to customize their services and communicatewith their friends. Such a relationship and feeling of ownership cangreatly increase the convenience of using a jukebox and its relatedservices while also decreasing intimidation, frustration, etc.

In certain exemplary embodiments described herein, the jukebox can bemade the centerpiece for music services as well as other services thatenhance the experience of users as well as the revenues of locationmanagers. For example, a jukebox can become a contact point at a givenlocation through which users can reach out to their friends. Forinstance, users may call a get together using the jukebox, share musicthrough the jukebox system, or meet up at a jukebox if they becomeseparated at a crowded club. Similarly, a jukebox can become, forexample, a contact point at a given location through which the managerof the location can reach out to customers. For instance, a manager canadvertise specials, notify regulars of special events, etc. Suchcommunications can be initiated by users, by location managers, or bythe jukebox itself.

When jukebox users leave a location, their connection to the music, and,more particularly, the jukebox itself, typically ends. Users providemassive amounts of data to the jukeboxes, such as, for example, whichusers like certain types of music or certain songs, when they listen tomusic, how frequently they listen to it, etc. With conventionaljukeboxes, this information is not leveraged to provide additionalfeatures and/or services to interested users. Thus, collectedinformation typically is wasted, and users experience only a fleetingsense of ownership. Users cannot, for example, recreate the experienceof a particular night out.

Proprietors also lose out, because their connection to jukebox usersdisappears when users leave their establishments. Thus, proprietors losecustomers until they return and are forced to rely on traditional, oftenignored, methods of bulk advertisement. This form of advertisingtypically lacks specificity and does not reflect a personalized sense ofbelonging for users. Additionally, proprietors also cannot recreatespecific events at which, for example, they had a particularlyprofitable nights.

Online communities typically, for example, on the Internet, havesprung-up to try to connect disparate users in a virtual space. Thesecommunities provide potentially continuous access to a broad range offeatures and users alike. However, conventional online communities arevirtual only—when a user steps away from a computer, the connection,quite literally, is broken. Thus, while users may access this broad hostof features and customize their experiences and even build an onlinepersona complete with, for example, buying and viewing habits, theexperience is fleeting.

By connecting jukebox users through an online community, however, theinformation provided to the jukebox can be used to provide a variety offeatures and services to the users. And, because jukeboxes are presentat thousands of meeting points, connections exist at thousands ofphysical locations apart from the online virtual community. Thus, byleveraging the data collected by jukeboxes and tying users to an onlinecommunity, a mixed real-and-virtual community may be established, forexample, creating a lasting sense of ownership, personalizing servicesfor potentially all users, drawing users together, establishing avibrant socially active community of users connected by music, etc.Proprietors may similarly benefit by, for example, achieving a pipelineto additional business by connecting with customers while they are awayfrom their locations, thus drawing them to their locations, etc.

In essence, a jukebox with an associated remote application can, forexample, change users' perceptions of jukeboxes. Jukeboxes need not bestand-alone devices accessible only at bars. Rather, the instantinvention allows users to consider jukeboxes as, for example, mediacenters, meeting points, portals to online communities, etc.

Moreover, with the advent of web-enabled portable devices (such as, forexample, cell phones, personal digital assistants, etc.), users even cantake the virtual community with them wherever they go. Users potentiallymay use portable devices to directly download music at any time, suchas, for example, when they hear a song at home, in the car, at a bar,etc.

There is a need for an improved jukebox system that addresses variousneeds of users, location owners, and operators. The instant invention isdesigned to address these and other issues and to provide enhancedfunctionality for such jukebox systems.

BRIEF DESCRIPTION OF THE DRAWINGS

These and other features, objects and advantages of the instantinvention will be further understood by review of the following detaileddescription of the exemplary embodiments when read in conjunction withthe appended drawings, in which:

FIG. 1 is a block diagram of a conventional downloading digital jukeboxsystem;

FIG. 2 is a block diagram of the improved downloading digital jukeboxsystem in accordance with a preferred embodiment;

FIG. 3 is an exemplary screen shot showing an initial selection screenin accordance with a preferred embodiment of the jukebox system;

FIG. 4 is another screen shot showing an exemplary search screen for usein searching for songs on the local server in accordance with apreferred embodiment;

FIG. 4A shows an exemplary process for using a Personal Music Assistantto search for songs that might be appropriate for a user-specifiedprofile;

FIG. 4B shows an exemplary process for using a Personal Music Assistantto search for songs that might be appropriate for a recognized user'sprofile;

FIG. 4C is an exemplary screen shot showing a non-limiting list ofgenres and themes available to a user in accordance with oneillustrative embodiment;

FIG. 5 is another exemplary screen shot showing the results of a searchon the local server and providing the user an option of downloading adesired song to the jukebox device for a fee, in accordance with apreferred embodiment;

FIG. 5A shows an exemplary process for searching through a list ofpopular songs;

FIG. 6 is another exemplary screen shot showing an alternative method ofallowing access to the downloading feature;

FIG. 7 shows a block diagram of a preferred embodiment of the localsever;

FIG. 8 shows a block diagram of an exemplary overall network includingcommercial jukeboxes and residential jukeboxes, as well as otherdownloading devices and associated connections that are managed by thejukebox system;

FIG. 9 shows an overhead view of an exemplary establishment layout for amulti-zone jukebox system;

FIG. 10 shows an overhead view of an exemplary establishment layout fora multi-zone jukebox system with selection terminals in each zone;

FIG. 11 is a flowchart showing an exemplary implementation of a zoneselection process for a multi-zone jukebox system;

FIG. 12 is a flowchart showing an exemplary implementation of a priorityplay by zone selection process for a multi-zone jukebox system;

FIG. 13 shows an exemplary implementation of a multi-zone set ofpriority and non-priority queues, with a subset of queues for each zone;

FIG. 14 is a flowchart showing an exemplary distribution andinitialization scheme for a jukebox with morph capability;

FIG. 15 is a flowchart showing an exemplary implementation of anautomatic jukebox morph initiation process based on a triggering event;

FIG. 16 is a flowchart showing an exemplary implementation of a jukeboxmorphing process;

FIG. 16A is an exemplary screen shot showing how a morph of a jukeboxcan be initiated in one preferred embodiment;

FIG. 16B is another exemplary screen shot showing how a user can specifyvarious criteria before a morph of a jukebox in one preferredembodiment;

FIG. 17 shows the relationship between a jukebox with expanded mediastorage and a central server;

FIG. 18 is a flowchart showing an exemplary process for a song selectionprocess when a song is not in the “standard” available playable songlist;

FIG. 19 is a flowchart showing an exemplary process for a priority playqueue with prioritization-based-on-bidding capability;

FIG. 19A is a flowchart showing an exemplary implementation of a jukeboxvoting process;

FIG. 19B(1) is an exemplary screenshot showing a voting queue display;

FIG. 19B(2) is another exemplary screenshot showing a voting queuedisplay;

FIG. 19C is an exemplary block diagram showing a voting mechanism withina given location;

FIG. 19D is another exemplary block diagram showing a voting mechanismwithin a given location;

FIG. 19E is an exemplary block diagram showing a voting mechanism foruse with multiple locations;

FIG. 19F is another exemplary block diagram showing a voting mechanismfor use with multiple locations;

FIG. 20 is a flowchart showing an illustrative process for using auser-tailored system for managing music, communications, etc. inaccordance with one exemplary embodiment;

FIG. 21A shows non-limiting, illustrative options available for editingaccount/profile information in one exemplary embodiment;

FIG. 21B shows non-limiting, illustrative options available for managingmusic in one exemplary embodiment;

FIG. 21C shows non-limiting, illustrative options available for managingbuddy lists in one exemplary embodiment;

FIG. 21D shows non-limiting, illustrative options available forcommunicating with others in one exemplary embodiment;

FIG. 21E shows non-limiting, illustrative options available foraccessing value-added content in one exemplary embodiment;

FIG. 22 is an exemplary screen shot of a login page in accordance withone exemplary embodiment;

FIG. 23 is an exemplary screen shot showing the features available aftera recognized user has logged in, in accordance with one exemplaryembodiment;

FIG. 24 is a flowchart showing an exemplary process for accessing asystem remotely in one exemplary embodiment;

FIG. 25 is a flowchart showing an exemplary process for selecting one ormore of a non-limiting list of services and/or features in a systemaccording to one exemplary embodiment;

FIG. 26A is an exemplary screen shot showing the features availablebefore a user logins into a system according to one exemplaryembodiment;

FIG. 26B is an exemplary screen shot showing the features availableafter a user logins into a system according to one exemplary embodiment;

FIG. 26C is an exemplary screen shot showing how a user might updateaccount information;

FIG. 26D is an exemplary screen shot showing how a user might manageplaylists;

FIG. 26E is an exemplary screen shot showing the results of anillustrative search for music;

FIG. 27 shows an exemplary system for downloading music to a mobiledevice;

FIG. 28 is a flowchart showing an exemplary process for retrievingmusic;

FIG. 29 is a block diagram of an improved downloading digital jukeboxsystem with remote devices accessing a jukebox from within a particularlocation;

FIG. 29A is a block diagram of an improved downloading digital jukeboxsystem with remote devices accessing a jukebox from within a particularlocation;

FIG. 29B is a block diagram of an improved downloading digital jukeboxsystem with remote devices outside of a particular location accessingthe digital jukebox system;

FIG. 29C is another block diagram of an improved downloading digitaljukebox system with remote devices outside of a particular locationaccessing the digital jukebox system;

FIG. 29D is a block diagram of an improved downloading digital jukeboxsystem with another downloading digital jukebox system outside of aparticular location accessing the first digital jukebox system;

FIG. 29E is another block diagram of an improved downloading digitaljukebox system with another downloading digital jukebox system outsideof a particular location accessing the first digital jukebox system;

FIG. 30 is an exemplary flowchart showing one way in which users maychange their status by becoming “verified users”;

FIG. 31 is an exemplary flowchart showing how registered users mayreceive credits for referring potential users; and,

FIG. 32 is an exemplary flowchart showing how registered uses mayreceive credits for creating public playlists.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS

Referring now to the drawings, FIG. 2 shows a block diagram of anexemplary preferred embodiment of an improved jukebox system 10′. Thejukebox system 10′ includes similar elements as shown in FIG. 1 anddescribed above, including a central server 12, communications network14, and remote jukebox devices 16, 16 a-16 f. However, the jukeboxsystem 10′ further includes local servers 22, 22 a-22 f respectivelyconnected to each of the jukebox devices 16, 16 a-16 f. The centralserver 12 includes a master library of songs (and/or other content).Each of the jukebox devices includes a subset of the master library on alocal storage device of the jukebox. The central server may be used toindividually manage the contents of the jukebox device, by monitoringusage of and updating the subset of songs on each of the jukebox deviceswith the intent of maximizing the usage thereof. The central server 12periodically receives data from each of the jukeboxes for the purpose ofroyalty accounting and payment for songs played. The jukebox devices mayconnect to the network in any suitable manner, such as dial-up modem orbroadband modem (e.g., DSL, cable, wireless broadband, or satellite).The communications network 14 may be any suitable network capable ofdistributing data (e.g., audiovisual data) from the central server 12 tothe jukeboxes 16 and enabling data to be uploaded from the jukeboxes 16to the central server 12.

The songs (and/or other data) are preferably digitized, compressed andencrypted by the central server 12 prior to sending songs to thejukeboxes for security and bandwidth purposes using known techniques.The songs are then decompressed and decrypted by the jukeboxes forstorage and reproduction thereon. Thus, each of the jukeboxes maintainsin a database a library of digitized songs for play on the jukebox,wherein the library can be changed or updated through communication bythe central server. The jukeboxes preferably also receive and store dataconstituting images (e.g., still and/or moving video and/or graphicalimages) that can be displayed on the display 18 of the jukebox device16. In one exemplary embodiment of the invention, the jukebox deviceshave similar structure and operation described in U.S. Pat. No.6,308,204 referenced above. Thus, the jukebox devices 16 each preferablyinclude one or more microprocessors, such as a main CPU and an audioDSP, a memory, such as a hard drive, for storing songs and/or othercontent, a display of displaying visual items, an audio arrangement 20for providing audio, a communication system for enabling the jukebox tocommunicate with the central server 12 through the communicationsnetwork 14, and operating software, preferably including a multitaskingoperating system, that controls the operation of the jukebox. Theoperating software is also preferably updateable through communicationwith the central server 12 as described, for example, in U.S. Pat. No.6,308,204 referenced above. The jukeboxes 16 further include one or morepayment devices, such as coin, bill and/or credit card input devices,for enabling a customer to pay for usage of the jukebox device in aconvenient manner. The screen 18 is preferably a touch screen thatenables the user to input selections by touching the screen.

Each jukebox device has, in one embodiment, a local server 22 that canbe accessed by the jukebox device. The local servers are respectivelyconnected to the jukebox devices using Ethernet or other type of localconnection. In another embodiment, the local server may simply be alogical extension (e.g. partition, directory, or area) of the jukebox'shard drive, rather than a separate hardware device. The local servers 22each preferably include a mirror copy of the master library of musicalrecordings maintained by the central server 12. The local server 22 canbe loaded with the master library by the entity that owns and/orcontrols the jukebox network prior to shipping the local server andjukebox device to the jukebox distributor or operator. Of course, overtime, the local sever will no longer correspond identically to thecentral server, due to the fact that the central server is preferablycontinually updated with additional or new songs. Thus, the localservers 22 are also preferably updated periodically to maintain acorrespondence with the library on the central server 12. This updatingcan be done, for example, by the central server 12 through communicationwith the jukebox devices connected with the local servers 22 using, forexample, either dial-up or broadband modems. Alternatively, the updatingcan be done personally with an update tool that can be connected by arouteman or other person directly to the jukebox or local server for thepurpose of updating the contents of the local server. The portable toolcould include a removable storage medium, such as a hard drive, thatcould be returned to and reused by the owner of the jukebox system forfuture updates. The tool itself could be kept by the operator or otherperson in charge of maintaining specific jukeboxes for use upon receiptof the updated removable storage medium from the owner of the jukeboxsystem.

For security reasons, the local server 22 preferably does not includeall of the digital data that constitutes any one song that is stored onthe local server 22. In addition, the part of the song that is on thelocal server is encrypted. The jukebox device 16 contains the missingpart of each of the songs on the local server, thereby enabling thejukebox to assemble the complete song based on the contents of the localserver and the memory on the jukebox device. The missing data located onthe jukebox is needed in order to decrypt the songs. For example, asingle block (or other small fraction) of data for each song may bemissing on the local server but present on the jukebox device, and theencryption may be based on the missing block and may proceed on a blockby block basis. Thus, none of the blocks can be decrypted withoutobtaining and/or decrypting a preceding block. This feature providessignificant security and prevents or deters theft or other type ofunauthorized use or copying of the songs on the local server. Thus, inthis embodiment, each local server must be specifically assigned to aspecific jukebox device so that the decryption described above can beproperly performed.

In accordance with a preferred exemplary embodiment, the local serversmay also each be individually registered with and identified to thecentral server 12, so that the central server can individually manageand monitor each local server. The same is true for the jukebox deviceitself, i.e., it may also preferably be registered with the centralserver so that it too can be individually monitored and managed by thecentral server. As will be understood from the foregoing description,the local servers become an important and advantageous part of thejukebox system by allowing the contents thereof to be accessed by thejukebox device to provide additional services (such as providingadditional songs) not available on the jukebox device itself. As will beexplained below, the song library of the central server and/or thestorage capacity itself can be advantageously used to provide servicesto other jukeboxes, such as fee-based residential and commercialjukeboxes and/or other fee-based equipment. One preferred use of thelocal servers may be to provide an immediate song downloading featurefor the jukebox device will now be described below in detail withreference to the exemplary screen shots of FIGS. 3-6.

FIG. 3 shows an exemplary screen shot for a music selection screen 30 asdisplayed on the touch display of the jukebox device. As can be seen inFIG. 3, this selection screen, which is preferably the initial selectionscreen displayed to a customer, includes graphical representations 32 ofthe various album covers for songs that are stored in the memory of thejukebox device. The albums covers are shown in alphabetical order andthe virtual slide bar 33 can be used to scroll through the availablealbums. Up and down arrows (34 and 35) are also provided for steppingthrough the available albums. A “Now Playing” button 36 is also providedfor showing information on the song currently playing on the jukebox (ifany). A “Top Ten” button 38 is also provided for showing a list of theten most popular songs on the jukebox. A “Tune Central” (TM ofTouchTunes Music Corporation) button 39 is also provided, the functionof which will now be described in detail with reference to FIG. 4.

If the user does not see an album of interest in the display of albumcovers or desires for any reason to search for available songs that arenot present on the jukebox device, the user may select the “TuneCentral” button 39. When the “Tune Central” button is pressed, thedisplay on the jukebox is changed from that of FIG. 3 to that of FIG. 4.The exemplary screen shot of FIG. 4 shows a search screen 40 whichenables a search to be performed on the local server 22 connected to thejukebox device. This screen 40 provides a virtual keyboard 42 for use inentering a search request. The search can be done by album, artist,song, or genres or themes (i.e. categorized lists of songs, preferablybased on popularity, that help a user find a particular song), based onthe associated buttons 47. Once a search is typed, the user touches the“Search” button 44 and a search of the contents of the local server isinitiated. Input from the virtual keyboard can be cleared using the“Clear” button 46.

Genres may comprise, for example, “pop,” “rock,” “country,” “rap,”“R&B,” “Blues,” etc. Themes may comprise, for example, “Christmas,”“Irish,” “Birthday,” etc. In some exemplary embodiments, these lists canbe retrieved from the server, while in other exemplary embodiments thelists may be built dynamically, based on, for example, certainparameters. In still other embodiments, the server may select whichlists to enable or send to the jukebox based on criteria, such as, forexample, location, music type, etc. A system might only display genresand/or themes for which music is downloaded. However, a system mightdisplay all genres and/or themes and enable download of other songs notavailable to the local jukebox. It also will be appreciated thatalthough FIG. 4C, discussed in detail below, shows the genres and themeson the same screen, other embodiments may present them separately.

FIG. 4C is an exemplary screen shot showing a non-limiting list ofgenres and themes available to a user in accordance with oneillustrative embodiment. Buttons 450 arranged on the left side of thescreen correspond to themes available to a user, while buttons 460arranged on the right side of the screen correspond to genres availableto a user. Button 470 exits this selection mechanism. It will beappreciated that other arrangements of the buttons are available, andthat the list of themes and genres provided is for non-limiting,illustrative purposes only.

Similar to the genres and themes search, a user may, for example, searchfor a song using a Personal Music Assistant, an exemplary process forwhich is shown in FIG. 4A. Preferably, after pressing a PersonalAssistant button (step 402), the jukebox would ask certain informationto identify the user if the user is not already identified (step 404).Such information could include, for example, age (or date of birth),preferred style, background, place of birth, or other information thatcould be used to generate a profile of the user. The jukebox thenpreferably could compare the profile information to selections made byother users with similar profiles (step 406) from, for example, thespecific jukebox, the particular establishment, or a national databaseand recommend songs (step 408). For example, the jukebox might suggest asong by “The Doors” to a male user from California who was born in 1960.The user could then choose a song from that list or initiate a newsearch (step 410).

Furthermore, instead of entering identifiers, as shown in FIG. 4B, thePersonal Music Assistant could recognize a user in other ways (step422), such as, for example, after a credit card or a pre-programmedsite-specific identification card is swiped by the jukebox. Preferably,the Personal Music Assistant would maintain a list of selections made bythe user. The user's list of selections could be maintained, forexample, on a local jukebox terminal, on a site's central jukeboxserver, on a remote server, or on an identification card, etc. After thePersonal Music Assistant recognizes the user, it could then recommendsongs based on, for example, songs by the artists the particular userenjoys (step 426), songs played frequently by the user (428), songs notheard recently by the user (430), etc.

Additionally, a Personal Music Assistant recognizing, for example, apreferred customer or a customer with a large number of credits mightmorph the jukebox into a jukebox more enjoyable to that specific user.In a related feature, certain patrons may “rent” a jukebox for, forexample, a special occasion. Accordingly, a patron could pay a certainamount of money to morph the jukebox into a particular type of jukebox.For example, a patron having a party (e.g. a birthday party) at aparticular location could rent a jukebox and morph it into a jukeboxthat allows only that patron's favorite songs. In another relatedfeature, a patron could exclusively rent a jukebox and prevent othersfrom selecting songs by, for example, programming a playlist throughanother device (e.g. the web or other communications network operablyconnected to the jukebox system) or by restricting access to the jukeboxthrough a password or the like. Credits could be, for example, purchasedby the user; or given to the user as a reward, for example, forpurchasing drinks or souvenirs at an establishment, or for being aregular repeat customer. Thus, a Personal Music Assistant could beimplemented in a manner that makes selecting songs a more enjoyable,dynamic, and responsive process while removing the immediate pressureplaced on the user to know which song to choose.

When a search is initiated from screen 40, the screen changes to thatshown in FIG. 5 to display the results of the search. As shown in FIG.5, the results of the search are listed. More particularly, in thisexample, a list of songs that satisfy the search request are listed. Thelist could also be by album if the search was album based. The user canscroll through the search results using slide bar 53. The user is alsoshown a display 55 of the number of current credits and a display 56 ofthe number of credits that are required to download a song from thelocal server to the jukebox device. The user can go back to the previousscreen by touching the “Back” button 57. If the user selects a song fromthe search list and then touches the “Get It Now” button 54, the jukeboxis operable to immediately download the selected song from the localserver to the jukebox for play on the jukebox. The downloaded song canbe queued up with any other selected but unplayed songs (if any) forplay on the Jukebox. In this example, the download costs five creditsinstead of one credit like a normal selection from the storage of thejukebox itself. Once the downloaded song is played, it may be deletedfrom the jukebox device (together with any graphical data, such as thealbum cover graphic) that was also downloaded from the local server inconnection with the song download). Preferably, however, the song willbe kept in a “smart cache” to determine if and/or when the song shouldbe deleted. For example, the song may be cached for a predefined period(e.g. a day, a week, two weeks, etc.) while the jukebox monitors playsof the song. If the number of plays are above a certain threshold forthe predefined period, for example, the song may be kept; if the numberof plays is below the threshold, the song may be deleted. The song mayor may not be added to the master list of readily available songs,depending on the specific embodiment of the invention—e.g. the song in“smart cache” may appear as if it is not readily available to the userwhile in fact it is stored on the jukebox in, for example, a protectedarea. In this way, the user has the option, through use of the “TuneCentral” button, to temporarily obtain on the jukebox any song from themaster library of recordings without the need to contact the centralserver 12. As a result, the jukebox provides a more enjoyable experiencefor the user, while also increasing revenue generated thereby.

Also providing an enjoyable experience for the user is the centralservers' capability to identify “hot hits,” preferably in real-time.Preferably, new songs could be made available in a master catalog—thatis, they need not reside on local servers or expanded media storage.Then, songs played frequently in a given area (ranging from, forexample, a single site or group of sites, to a state or country, to aglobal connection) could be identified as popular. These songs, or “hothits,” preferably could be downloaded by, or sent to, individualjukeboxes. Individual jukeboxes preferably would maintain lists of “hothits” in real-time, allowing users to search through the most popularsongs at any given time. Alternatively, a jukebox might maintain a listof “hot hits” without downloading the popular songs, thereby potentiallysaving download time and resources. As a result, the jukebox couldprovide an enjoyable experience for the user by providing easy access tothe most popular songs. Thus, a jukebox may have access to a “hot list”of “hot hits” generated by a jukebox, jukeboxes, designated by anoperator, created automatically and/or especially for enabled jukeboxes,etc. This “hot list” may work as an alternative to themes and/or genres,and/or it may function with themes and/or genres to provide the mostpopular (“hot”) songs within a given theme and/or genre.

FIG. 5A shows an exemplary process for maintaining a “hot list” on ajukebox with a broadband connection. It should be noted that the sameprocess could apply for a system with a different type of connection,though more time and resources may be used to download a song over aslower connection. In step 502, songs from a master catalog are receivedby a site's central server. Of course, it should be noted that songscould be stored to a local jukebox's storage media. In step 504, a userusing a jukebox terminal would select a “Hot List” button. After the“Hot List” is displayed (step 506), the user could select a particularsong or initiate a new search (508).

FIG. 6 shows another exemplary screen shot of a song selection screen 60that is displayed when a user touches an album cover graphic from thescreen 30 of FIG. 3. Thus, this screen shows an alternative (or typical)method of selecting a song, wherein the song is selected directly fromthe subset of songs that are directly available from the storage deviceof the jukebox itself (rather than the local server). In this example,Joe Cocker's Greatest Hits was selected from the screen of FIG. 3. Asshown in FIG. 6, the resulting screen display 60 shows the selectedalbum graphic 61 and a list of the songs 62 that are available on thejukebox for that album. The jukebox may or may not include all of thesongs for a particular album. The available songs can be scrolledthrough if necessary using scroll bars 63 a and 63 b. The user has theoption, through the “Play” button 65, to select a song from the list forplay on the jukebox. A “Play Now” button 66 is also provided forenabling the user to select a priority play of the song, thereby givingthe song a higher priority than songs selected using the “Play” button65. This priority feature preferably requires more play credits than thenormal play. A display 67 shows the number of credits available for theuser. Button 64 shows other albums for the same artist being shown at61, thereby enabling a user to easily search through the albums for aparticular artist for a desired song.

As also shown in FIG. 6, a “Tune Central” button 68 is displayed thatenables the user to search for songs by this same artist on the localserver as explained in connection with FIG. 4. In other words, button 68takes the user to the search screen 40 of FIG. 4 for searching the localserver. The user can then proceed to search the local server and selectsongs therefrom, if desired, as described above in connection with FIGS.4 and 5. Thus, as explained above, the user can access the local serverat various screens in a convenience and efficient manner, depending onthe desires of the user when interacting with the jukebox screen.

As can be seen from FIGS. 3-6, the user is provided with the option ofplaying songs that are resident on the jukebox device itself or,alternatively, selecting songs from the local server for download andplay in an efficient and reliable manner, thereby significantlyimproving the operation of jukebox systems, particularly those thatcannot quickly, easily or reliably receive downloads of music on demandfrom a central server. It is noted that the screen shots of FIGS. 3-6are only exemplary and any suitable screen configurations can be used toprovide the functionality described herein. In addition, the jukeboxoperator is provided with the ability through operator screens (notshown) to set filters per genre or style of music in order to limitaccess to the end user and avoid undesirable music being played at aspecific location. For example, these features preferably are availablethrough schedules defined by a jukebox operator and/or location manager,enabling, for example, a location manager to prevent hard rock or heavymetal music to be played before 11 am. The same features can be used,for example, by operators or location managers to configure playlistsand/or set the available music selections for particular dates and/ortimes. For example, operators or location managers may wish to restrictmusical selections to Irish music on Saint Patrick's Day, love songs onValentine's Day, Frank Sinatra music during dinner hours, etc.

In still other exemplary embodiments, a location might provide a“Virtual DJ.” According to one such system, a prepared playlist would beprovided to the jukeboxes of a location. Preferably, the playlist can betailored to the details of the location and/or the event to take place,such as, for example, locale, theme, target audience, etc. Furthermore,some illustrative playlists could be created by famous DJs to attractpatrons. DJs could attach their names to playlists and associatethemselves with various locations, even though they are not present. Aplaylist might extend for several songs or for several hours, dependingon the needs of the location. It is to be appreciated that coinage neednot be collected during such a Virtual DJ event, as a special fee can beassociated with the service of using a special playlist. It also is tobe appreciated that DJs may prepare special playlists for one-time use,or they may make available repeatable special playlists. Theserepeatable playlists may, for example, be downloaded by jukeboxes orprovided to the jukebox in any suitable manner. Thus, making third partplaylists available for use on the jukebox for a fee provides a wholenew revenue source for the jukebox operators, location owners andplaylist generators, such as well-known DJs or the like. When a playlistis made active, the normal functions of the jukebox are preferablystopped during play of the songs on the playlist.

FIG. 7 shows a block diagram of the electronic elements that define thelocal server 22 in accordance with an exemplary embodiment. As shown inFIG. 7, the local server 22 includes a CPU 72 (e.g., AMD Elan 800 MHz),a flash memory (e.g., 8 MB) containing the BIOS and OS, a pair ofmaster/slave hard drives (82, 84 and 86, 88, respectively), a pair ofIDE controllers 78 and 80 for the hard drive pairs respectively, a RAM76 (e.g., 32 MB), an Ethernet controller for controlling communicationwith the jukebox device 16, and the appropriate buses interconnectingthe various elements. Of course, other configurations or arrangementsfor the local server 22 may be used. A unique identifier may be providedin the local server for enabling the local server to be uniquelyidentified and registered by the jukebox and/or central server. Theidentifier may, for example, be located in the flash memory 74.

As will be appreciated from the description of the invention above, theaddition of the local server significantly enhances the operation of thejukebox devices that are part of a jukebox system. However, the localservers also provide other benefits and features that will now bedescribed.

A collection of local servers 22 may be used as a network of distributedservers that can be controlled by the central server 12 through itsassociated jukebox device 16 to provide music services to other devices.For example, the local servers and associated jukebox can be used todeliver requested songs to a dedicated residential or commercial jukeboxdevice (or other suitable jukebox device) in addition to providing songservices to the specific jukebox to which it is connected and assigned.Thus, the network of distributed servers can provide a support networkfor implementing residential and commercial jukeboxes of the type whichallow a user to download songs for reproduction and/or storage at aresidential or commercial location for an appropriate fee. As a result,the jukebox system operator can provide and control commercial jukeboxesand well as residential jukeboxes through the jukebox system. In thisembodiment, the jukebox device and/or local server are connected to theInternet (or other suitable network) using a broadband modem and isprovided with software that can selectively deliver song files to anydedicated residential jukebox device (also connectable to the Internet)under control of the central server. The central server receivesrequests from a residential jukebox and, by analyzing traffic on thenetwork, provides instructions to a selected jukebox device to downloadthe requested song file (either from its memory or from the localserver) to the residential jukebox for a fee or under a subscriptionplan for the residential jukebox. In certain exemplary embodiments,requested songs may be streamed to a jukebox. It will be appreciatedthat streamed media may originate at a dedicated server, a network ofstreaming servers, from a jukebox or jukeboxes (such as peer-to-peer ormultipeer downloading), etc.

In accordance with another exemplary aspect of the invention, the localserver and jukebox device are used, under control of the central server,to provide management services for other types of coin operated orpayment triggered equipment, such as gaming devices, installed in thesame location as (or in close proximity to) the jukebox. In other words,the jukebox system is preferably used to update the functionality ofand/or manage other downloading devices present in the same location. Asa result, the jukebox becomes a “central hub” for all downloadingequipment in a location. This feature is achieved, in one embodiment, bynetworking all of the downloading devices in a single location togetherwith the jukebox and local file server. The central server can thendownload information to the local server together with instructions tothe jukebox as to which devices should updated with what data and/orsoftware. The jukebox device and central server can also be used tocollect information from the other downloading devices to which it ismanaging and upload that information to the central server forreporting/accounting purposes. Thus, the owner/operator of the jukeboxsystem can act as a third party service provider to other coin-opcompanies for the purpose of managing and/or updating their equipment.

The large amounts of memory provided by the local servers and the factthat they are provided and accessible at thousands of locations over awell controlled network, turns the jukebox system into a powerful toolthat can be used to perform a variety of functions in the coin-opindustry. More and more coin-op manufacturers are going towards gamesthat are software upgradeable through their internal hard drives. Theseupdates are done periodically, but as these devices increase there willbe an ever increasing need for a system that can reliably andefficiently perform the updates from a remote location. The jukeboxsystem described herein satisfies this need by enabling all suitableelectronic coin-op devices at a jukebox location to be managed by thecentral server using the jukebox and local server at the location. Thecentral server can download software or data updates, store them on thelocal server and then dispatch the updates to the intended units ofequipment in the establishment. Thus, the jukebox system can act as athird party service provider to other companies in the coin-op business,thereby significantly enhancing the functionality of the jukebox system.

As an example, there are currently about 140,000 Merit coin-operatedcountertop devices in the USA, each of which enables users to play gamesand the like for a fee. Many of these devices operate with a hard drivethat can be upgraded with new software. Merit does this by shippingCD-ROMs to operators who then need to drive to each location andmanually update each machine. In accordance with the instant invention,however, all suitable coin-op equipment at a location are connected(directly or indirectly) with the local jukebox and local serverassigned thereto. This enables the central server to receive theintended software update for any device, together with information thatidentifies what devices are to be upgraded with what software. Theupgrade services are preferably fee based and provide an additionalrevenue stream for the jukebox system. The central server then downloadsthe software to the local servers with the upgrade instructions tofurther download the upgrades to the appropriate device(s).

As explained above, the local server enables songs to be downloaded to acommercial jukebox to which it is assigned or to residential jukeboxesunder control of the central server. In addition, the local servers canbe used for an on-premise networked application which manages othercoin-op devices. These various features of the instant invention areillustrated in FIG. 8.

FIG. 8 shows a block diagram of a complete jukebox system network ascontemplated by an exemplary embodiment. As explained above, the systemincludes a central server 12 connected to a communications network 14, aseries of commercial jukeboxes 16 a, 16 b and 16 c with associated localmusic file servers 22 a, 22 b and 22 c, a series of residentialjukeboxes 100 a, 100 b and 100 c connected to the network via broadbanddevices 102 a, 102 b and 102 c, and an on-premise network shown on theright hand side of FIG. 8. This on-premise network includes a jukeboxdevice 16 d connected via a router or network hub 110 to a local fileserver 22 d, a number of additional coin-op equipment, such as a dartgame 104, a golf game 106 and a countertop videogame 108, and abroadband modem 112 connecting this local network to the communicationsnetwork 14. With this exemplary configuration as shown in FIG. 8 all ofthe functionality described herein can be implemented through thejukebox system of the instant invention.

FIG. 9 shows an overhead view of an exemplary establishment layout for amulti-zone jukebox system, in accordance with one embodiment of theinvention. In accordance with an exemplary embodiment, the establishmenthas three zones 121, 123, 125. Each zone is equipped with its own set ofspeakers 127, 129, 131, which are operably connected to the jukebox 133.Different music may be played simultaneously in all three zones 121,123, 125 and all the music may be played from a single jukebox 133. Thejukebox 133 may be provided with additional hardware, as needed, toallow this implementation.

Alternatively, the user may elect to have a song played in more than oneof the zones 121, 123, 125 simultaneously, or in more than one of thezones at different times. The user may have to pay additional credits toimplement either of these features. A preferred embodiment of amulti-zone system could play music at a high quality in the differentzones using the system described in application Ser. No. 11/023,390,filed Dec. 29, 2004, entitled “Wireless Digital Transmission System forLoudspeakers,” which is a continuation-in-part of Ser. No. 09/161,584,filed on Sep. 28, 1998. The entire contents of both applications isincorporated herein by reference. Using this system, for example, ajukebox could compress and transmit audio data through AC power lines toan addressable location, where it could be received, decompressed,converted, and played. In fact, any of the jukebox components hereincould be implemented in a manner that uses AC power lines as acommunication network for operation.

It is to be appreciated that Wireless Digital Transmission System can beused for other purposes in other embodiments where data needs to be sentbetween two or more devices. For example, this system could be used toconfigure dummy terminals. In such an embodiment, the Wireless DigitalTransmission System could be used to send information such as, forexample, whether to morph, what songs are appropriate given a particularmorphing of the jukebox, the zones in which selected music should beplayed, maximum volume levels, etc, in addition to sending music to thespeaker systems.

The operator may also restrict what kind of music is available in agiven zone, based on the type of activity in the zone, the time of day,or any other suitable selection criteria. For example, in FIG. 9, zonethree 125 is a restaurant. Restaurant patrons may not wish to listen tothe same type of music as someone in zone one 121, which is a bar roomin FIG. 9, or in zone two 123, which is a pool room. The operator mayrecognize this and restrict the type of music that can be played in zonethree 125. Alternatively, the operator may restrict the volume of themusic in any given zone. For example, patrons of a pool room 123 or arestaurant section 125 may not want the music as loud as it is desiredto be in the bar room 121. And maybe the restaurant section 121 is to bekept quieter even than the pool room 123. The owner can adjust andcontrol all suitable settings to provide the most versatile, patronfriendly environment in each of the zones, based on any suitablecriteria.

FIG. 10 shows an overhead view of an exemplary establishment layout fora multi-zone jukebox system with selection terminals in each zone. Inaccordance with an exemplary embodiment, the bar has three zones 121,123, 125. Each zone is equipped with its own set of speakers 127, 129,131, which are operably connected to the jukebox 133. Different musicmay be played simultaneously in all three zones 121, 123, 125 and allthe music may be played from a single jukebox 133. The jukebox 133 maybe provided with additional hardware to allow this implementation.

In the embodiment of FIG. 10 there are also one or more “dummy”terminals 137, 139 located throughout the establishment. An exemplaryillustrative dummy terminal could use X-server technology. Theseterminals 137, 139, which may be stand alone devices or may be providedas part of the interface on a gaming machine or other suitable devicewith a digital display, allow selection of songs from the jukebox 133for the zone in which they are located (or possibly other zones). Theseterminals 137, 139 duplicate the zone restrictions imposed on the mainjukebox interface and selection criteria. The terminals 137, 139 may berestricted to only allowing selection of music for play in the zonewhere each respective terminal is located, or they may allow selectionfor play in one or more different zones.

Additionally, the graphical interface of the terminals 137, 139 maychange in accordance with available selections, themes of the bar,themes of the room in which each terminal is located, or any othersuitable criteria.

FIG. 11 is a flowchart showing an exemplary implementation of a zoneselection process for a multi-zone jukebox system. In accordance with anexemplary embodiment, the jukebox first begins the transaction 141 withthe user. The user is instructed to select a song 143, and select one ormore zones 145 in which the song is to be played. The jukebox thendetermines the price based on the number of zones selected 147. Thejukebox accepts payment from the user 149 and queues the song for playin the selected zone or zones 151. Next, the jukebox checks to see ifthe user would like to select another song 153. If the user wantsanother song, the process returns to the select song step 143 andrepeats from there. If the user is finished making selections, theprocess ends 155.

FIG. 12 is a flowchart showing an exemplary implementation of a priorityplay by zone selection process for a multi-zone jukebox system. Inaccordance with an exemplary embodiment, certain jukebox systems may beprovided with one or more priority queues corresponding to one or morezones. If priority play is provided for a zone or zones, the jukeboxfirst checks to see if the user would like to select priority play forthe selected song 161. If priority play is selected, the jukebox thenprovides an option for the user to choose a zone or zones in whichpriority play should occur 163. Based on the number of zones selectedfor priority play, the jukebox determines a price 165, and acceptspayment of that price 167 from the user. The jukebox then places thesong in a priority play queue for each selected zone 169.

FIG. 13 shows an exemplary implementation of a multi-zone set ofpriority and non-priority queues, with a subset of queues for each zone.In accordance with an exemplary embodiment, each of N zones 171 may beprovided with its own set of queues, comprising a priority queue 175 anda non-priority queue 173. A list of songs selected for play ismaintained within each queue 173, 175. Each song in each queue may beprovided with an identifier 177, 179, which identifies the song, and/orthe position of the song in the queue, and/or any other suitablefactors.

FIG. 14 is a flowchart showing an exemplary distribution andinitialization scheme for a jukebox with morph capability. In accordancewith an exemplary embodiment, the contents of a factory drive aredefined at the point of manufacture 181. This same drive (or expandedmedia storage) may be shipped out with all jukeboxes 183, and may, forexample, only contain a subset of the total number of songs available onthe central server. This features simplifies the manufacturing processby enabling the identical drive to be shipped with all jukeboxes. Oncethe jukebox containing the drive has reached its destination, theoperator may select a subset of songs on the drive as the basic playablelist 185. This selection can be made based on the type of establishment,the type of music the establishment's patrons typically prefer, or anyother suitable criteria. The operator may also allow the central serverto recommend a basic playable list. The drive may also allow selectionof songs not on the basic list, but present on the factory drive, for anadditional fee 187. This list of “alternate” songs might not include allsongs however, as the operator might desire to restrict access to songsthat don't meet the theme of the establishment. For example, a countrybar owner might not ever want to allow selection of rap or hip-hop songson the jukebox. In certain exemplary embodiments, a jukebox will shipwith a large number of songs (e.g. 25,000 songs) on a very large storagemedium, such as, for example, a hard drive, flash media, etc. Thejukebox according to this embodiment would be without a “personality”until an operator and/or owner selected a subset of all songs to makeavailable to patrons. In this way, operators and/or owners can define“personalities” for their jukeboxes through definition of the basicplayable list.

Once the songs on the drive have been appropriately categorized (i.e.the basic playable list has been defined), the jukebox begins operation189. As long as a new basic playable list is not desired 191, thejukebox continues to operate 189 with the currently selected basicplayable list. If a new basic playable list is desired 191, the jukeboxmorphs 193 into a “new” jukebox, selecting a different playable subsetof songs for basic selection 185, and preferably changing additionalcharacteristics (e.g., graphics, ads, look and feel, etc.) of thejukebox as dictated by the morph. The ability to morph jukeboxes thusenables owners and/or operators to maintain a single jukebox with aplurality of triggerable personalities which can be switched betweenautomatically, at pre-defined events/times, manually, etc.

FIG. 15 is a flowchart showing an exemplary implementation of anautomatic jukebox morph initiation process based on a triggering event.In accordance with an exemplary embodiment, the user may define an event201, for example a themed night or a time of day, as a triggering eventwhich triggers a jukebox morph. The jukebox then operates as normal 203,checking periodically to see if the triggering event occurs 205. If thetriggering event has not occurred, the jukebox simply continues tooperate 203, but if the triggering event occurs, the jukebox is morphedinto a “new” jukebox. The triggering events may be one time events, orthey may be scheduled to occur weekly, daily, monthly or scheduled basedon any other suitable criteria. It should be noted that in a multi-zoneconfiguration, different zones may be morphed while others do notchange. This feature of the illustrative embodiments allows, forexample, a given zone or zones to be dedicated to a certain kind ofmusic while the other(s) may vary based on any variety of factors, suchas the time of day, an owner's desire to change the music, or a user'srequest.

FIG. 16 is a flowchart showing an exemplary implementation of a jukeboxmorphing process. In accordance with an exemplary embodiment, when thejukebox begins morphing 211, it selects a new subset of songs to be thebasic playable list 213. The jukebox then allows some or all of theremaining songs on the jukebox to be selected for an enhanced fee 215.Some of the remaining songs may be restricted based on what triggeredthe morph. Other characteristics of the jukebox may also change 217, forexample, the user interface may be changed, and different advertisingmay be displayed which corresponds with the predicted tastes of thecrowd for which the jukebox has been morphed. Other suitable changes mayalso be made. In one example of a preferred embodiment, a club owner hasa hip-hop night on Wednesdays, beginning at 9:00 pm and ending at 4:00am. At 9:00 pm on Wednesdays, the jukebox morphs into a hip-hop jukebox,with a basic selection of appropriate music. In accordance with themorph, the jukebox blocks all access to genres of music such as countrymusic, classic rock, jazz, blues and oldies, and the jukebox limits theavailable selection of hard rock additional songs to “hip-hop-esque”hard rock songs. The graphics on the jukebox convert to edgy, urbangraphics, and the advertising changes accordingly, displaying productssuch as apparel, drinks, and goods which should appeal to the hip-hopcrowd. At 4:00 am, the jukebox morphs back into the “standard” jukeboxfor that club, or into any other suitable jukebox. Alternatively, thejukebox may remain set in hip-hop mode until the next triggering eventoccurs. Again, it should be noted that in a multi-zone configuration,different zones may be morphed while others do not change. In the aboveexemplary non-limiting embodiments, the system might morph into hip-hopin one zone for the night, while the “standard” music for the clubremains playing in another area.

FIG. 16A is an exemplary screen shot showing how a morph of a jukeboxcan be initiated in one preferred embodiment. Area 160 is blank toindicate that no selections have been made. A user will select amorphing option by choosing, in this exemplary embodiment, for example,either TouchTunes Master button 162, Dynamic Master button 164, or Clonea Location button 166. It is to be appreciated that other embodimentsmay provide further morphing options in place of or in addition to theaforementioned buttons. In this embodiment, pressing the TouchTunesMaster button 162 will populate area 160 with a list of masterselections pre-selected by the TouchTunes music department. These masterselections may include, for example, collections of specific songs(e.g., all songs by British bands, all songs by a particular artist,etc.), ratios of particular themes or genres (e.g., a mix of 75 percentHip-Hop and 10 percent Pop, 10 percent Rock, and 5 percent techno for aparticular dance club feel, etc.), etc. A user may peruse the list usingslider bar 170. Once the user is satisfied, pressing Morph It button 168will morph the jukebox. It is to be appreciated that pressing the MorphIt button 168 may trigger an immediate morph, or it may save the morphand instead initiate it at a predefined trigger time. It also is to beappreciated that morphing data may be stored for morphing the jukebox onwhich the selection was made or any number of connected jukeboxterminals.

Pressing Dynamic Master button 164 is one exemplary, non-limiting way ofproviding increased user control over the morph. FIG. 16B is anotherexemplary screen shot showing how a user can specify various criteriabefore a morph of a jukebox in one preferred embodiment. A discussion ofthe buttons with identical numbers in FIG. 16A and FIG. 16B is omitted.Designations for the genres and/or themes of music are provided, suchas, for example, Rap label 172. To specify a given percentage of musicto be played, a user may press increase button 174 or decrease button176. The amount of music selected for that particular genre or themewill appear in a theme music amount area 178, while details about thetotal amount of music selected will appear in total music amount area180. In a preferred embodiment, a user may specify percentages of agenre and/or theme to play. For example, a user may select only 100percent Country music for a country night. Alternatively, as anothernon-limiting example, a user may select a mix of World and Latin musicfor an international feel. It is to be appreciated that although apreferred embodiment uses percentages, other embodiments may usedifferent measures for specifying how many of which type of music shouldplay, such as, for example, the number of songs in a given category, theamount of playtime in a given theme and/or genre, etc. It also is to beappreciated that in other embodiments, a user need not use the buttonsto increase or decrease the amount of music; that is, in otherembodiments, a user may directly input the amount of music via an inputmechanism. Thus, it is to be appreciated that morphing may be definedand/or triggered by a remote device operably connected to a jukebox.

When a user presses Clone a Location button 166 (e.g., from FIG. 16A orFIG. 16B), the jukebox displays a list of the jukebox devices,preferably including a unique identifier for each jukebox device. Inother embodiments, however, the list may include, for example, otherlocations owned by the same owner of the present location, etc. Afterselecting the jukebox terminal, the present jukebox could morph intothat jukebox. Alternatively, the jukebox selected could morph into thepresent jukebox, thus providing, for example, remote morphing. Stillalternatively, the list might include information about non-digitaljukeboxes that exist in addition to the digital jukeboxes preferred bythe exemplary embodiments. This morphing feature can allow users toreplace existing jukeboxes quickly and easily by allowing the newjukebox to morph into an older jukebox that is being replaced, such as aconventional record, CD or digital jukebox. Additionally, operators whomaintain multiple jukeboxes may, for example, apply a route-basedcloning and/or morphing process to provide, for example, a custom orparticularized set of songs.

Still further, a user can morph a location based on a location's data,specific to, for example, a given date or the latest data known. Thisallows users to morph a jukebox based on, for example, the popularity ofa given morph—e.g., users may choose to revert to a successful morph totry to recreate the entertainment of that evening. This feature alsoenables users to recover from hard drive crashes and/or other jukeboxfailures. For example, if a hard drive has been replaced after an oldone crashes, a user may morph (or clone) an existing location at a givendate and/or time before the crash to restore the songs that wereavailable before the crash because, preferably, the server maintainsinformation sufficient for this functionality. Thus, using the morphingfunction gives users increased control while also providing backup andrestoration features.

FIG. 17 shows the relationship between a jukebox with expanded mediastorage and a central server. In accordance with an exemplaryembodiment, the central server 221 contains a master library of songs,such library comprising all songs that are currently available to bedownloaded and all songs currently installed on jukebox hard drives. Thecentral server may communicate 222 with the remote jukebox 225containing a local hard drive 223. The hard drive 223 on the jukebox mayhave several sections, including available space for downloads 227,space occupied by preloaded songs 228, and space for software and anoperating system 229. Additional suitable sections may be added, forexample, a section containing different pictures for altering the GUI.The jukebox 225 may communicate with the central server 221 to downloadsongs, upload usage information, update software, and perform any othersuitable functions.

FIG. 18 is a flowchart showing an exemplary process for a song selectionprocess when a song is not in the “standard” available playable songlist. In accordance with an exemplary embodiment, the user first selectsa song 231. The jukebox checks to see if the song is available on thelocal hard drive as a “non-standard” selection 233. If the song isavailable on the local hard drive, the jukebox charges the customer theprice set for obtaining and playing a non-standard song 235 and playsthe song 237 (or adds it to a playlist, when appropriate).

If the song is not available on the local hard drive, the jukebox checksto see if a high-speed connection to the central server is available239. If there is no high-speed connection, the jukebox informs the userthat the song is temporarily unavailable 241 and orders the song fordownload 243. The jukebox may or may not charge an additional amount forordering the song. If, however, there is an available high-speedconnection to the central server, the jukebox orders the songimmediately and uses the high-speed connection to download the songright away, queuing it up for playing 245. The jukebox then charges thecustomer the price of a non-standard selection 247. In certain exemplaryembodiments, a jukebox may retrieve songs offline, either after alocation closes or before it opens. In certain exemplary embodiments, ajukebox may immediately download a song over a dedicated line with adial-up connection. In certain other exemplary embodiments, a song maybe downloaded from another jukebox (or other jukeboxes) rather than froma central or limited database to reduce network strain. In certainexemplary embodiments, the jukebox may download songs via a distributedmedia service in which portions of a given song may be downloaded from aplurality of sources and reassembled for the target jukebox. It is to beappreciated that such a peer-to-peer (or jukebox-to-jukebox) ormultipeer (several jukeboxes to jukebox) digital downloading networkwill need to track song licensing information. In certain exemplaryembodiments, if a song is not available on a jukebox but other versionsor covers are available, the jukebox may recommend to these other songsto the searching user. For example, a user searching for an unavailableTrisha Yearwood version of “How Do I Live” may be recommended availableversions by Dolly Parton and/or LeAnn Rimes. Preferably, recommendationswill be smart enough to ignore similarly named songs that are completelydifferent, such as, for example, the Everly Brothers' “Oh, Pretty Woman”and the Motley Crue's “Pretty Woman.”

The factory drive explained above, combined with the morphingcapabilities, eliminates the need for the local server explained above,as the factory drive can prove the same services as the local server,without the need for a separate hardware device. In other words, thefactory drive embodiment herein enables a jukebox to be shipped with asingle mass storage device of any technology (or multiple technologiesand/or multiple devices acting as a single mass storage device), whilestill enabling a basic playable list to be defined, an expanded playablelist to be defined, morphing capabilities, local server services to beprovided, as well as all other features described herein. The content ofthe factory drive, as shipped, is preferably defined using historical,statistical information on customer preferences.

FIG. 19 is a flowchart showing an exemplary process for a priority playqueue with prioritization-based-on-bidding capability. According to anexemplary embodiment, the user first indicates that he would likepriority play 251. The jukebox then displays the current status of thepriority play queue 253. This display may include information such ashow many songs are in the queue, what the top bid is, how much has beenbid on each song, which songs are “locked in,” and any other suitableinformation about the priority queue. The jukebox then allows the userto select how much additional money the user would like to pay to placehis song in a particular spot on the priority list and accepts paymentin the selected amount 255. After accepting the payment 255, the jukeboxplaces the song in a position on the priority list corresponding to theadditional amount received from the user 257.

Alternatively, in another exemplary aspect of the illustrativeembodiments, a user can bid on the right to have a song played beforeother songs previously selected for priority play are played. In apreferred embodiment, the user is shown the top price paid for apriority play, and can pay more than that price to obtain the highestpriority available.

Another exemplary aspect of the illustrative embodiments does not allowa user to be shown how much anyone else has paid for priority. The usercan pay however much the user desires to spend to obtain a priorityranking, and then receive a ranking of priority based on the amountpaid.

In accordance with a further exemplary aspect of the illustrativeembodiments, a user can pay however much the user desires to spend toobtain a priority ranking in accordance with the previous exemplaryaspect, and then be shown the priority spot which has been obtainedbased on the paid amount. If this spot is not satisfactory to the user,the user can pay additional money to move the song up in priorityranking, and be shown the new priority ranking obtained based on theadditional money paid. The user can repeat this process until thedesired priority ranking has been obtained. The user can also payadditional money to make it harder for other users to pre-empt theselected priority spot on the list in a bidding-type situation. Anyother suitable method of increased-pay-for-increased-priority may alsobe implemented.

In accordance with an additional exemplary aspect of the illustrativeembodiments which may provide a “lock in” feature, a user can “lock in”a priority ranking with a payment of a pre-selected amount. For example,if a user pays 15 credits to obtain a ranking of 3.sup.rd in priority,and wishes to guarantee the third ranking, the user may pay, forexample, 4 more credits to “lock in” the ranking. Since locking in theranking may require the “lock in” of all the rankings above the user aswell, the user may be required to pay a certain amount to “lock in” allsongs above the user's selection. In one such situation, the user caneither choose to pay the price quoted for the “lock in” or pay the sameor a varying amount of credits in an attempt to prevent futureover-bidding or to move the user's song up further in the priority list.

In accordance with another exemplary aspect of the illustrativeembodiments, any of the aforementioned bidding strategies may beimplemented, and the user may be shown how much everyone has paid fortheir particular rankings. This allows the user to know exactly how muchhe will have to pay to obtain a certain priority position. If the “lockin” feature is implemented, this will also let a user know if it ischeaper to pay the price to “lock in” the song or to pay to move up onthe priority list. All of these options result in increased revenue forthe operator.

It should be noted that although the embodiments above describe a systemfor distributing media to non-movable jukeboxes, alternative embodimentsusing similar systems could distribute media to portable jukebox devicesand are contemplated by, and within the scope and spirit of, thisinvention. A portable jukebox may be, for example, a PDA, a cell phone,or any other movable device capable of receiving and playing music.Furthermore, media may be distributed to portable jukeboxes using theabove described methods (e.g. through a broadband connection, wirelessconnection, etc.), or any other appropriate method, more suited to theparticular portable device, such as, for example, using Bluetoothtechnology. Additionally, the jukeboxes described above typically arefor commercial purposes. However, jukeboxes for other purposes such as,for example, playing residential media, also are contemplated by, andwithin the scope and spirit of, this invention.

In other exemplary embodiments, an employee of a location with a jukeboxcan be rewarded based on the number of plays customers pay for on thejukebox. In one such exemplary embodiment, the system keeps count of howmany plays have been paid for by customers. Every time a certain numberof plays have been paid for, the bar employee receives one free play. Insome embodiments, a separate counter will be maintained, while in othersembodiments only one counter may be necessary to calculate the number offree plays available. Thus, certain exemplary embodiments encourageemployees to promote the jukeboxes by compensating the employee withfree plays. This also can help reduce the similarity of song-selectionthroughout the day, preserve free plays for employees of differentshifts, etc.

Similarly, jukebox users may vote for particular instances of media toalter their priority in playlists. In this way, jukebox users can, forexample, “battle” for control over the music to be played in aparticular zone or particular zones within or among locations. It willbe appreciated that this voting/battle mode may be implemented by using,for example, a dynamic queue, a priority queue, multiple queues, etc. Italso will be appreciated that a jukebox could put into a voting modeautomatically (e.g. at a particular time of day and/or on a particularday of the week), or it could be triggered manually. FIG. 19A is aflowchart showing an exemplary implementation of a jukebox votingprocess. Unlike conventional jukebox operations, or even jukebox biddingmodes, a list of songs in a jukebox queue is displayed to users in stepS1902. This list may be generated automatically, by operators, barmanagers, patrons at a bar, etc. The list could be displayed, forexample, on a jukebox, or, more preferably, on one or more stand-alonemonitors. Additionally, in certain example embodiments, the list couldbe viewed by a plurality of mobile devices and/or terminals. Preferably,the information displayed contains at least the artists and names ofcoming songs, and a number associated with the priority of those songs.The list should be sorted by this number, so that the song with the most“votes” is displayed as the “next” song to be played, followed by thenext highest song, etc. Step S1904 determines whether the currentlyplaying song is over. If it is over, step S1906 removes it from thequeue, and the next song is played in step S1908. In another embodiment,users could vote to stop/skip the currently playing song (or instance ofmedia) by, for example, exceeding the number of votes the song hadbefore the jukebox started playing.

As users see the coming songs, they will be tempted to push up the songsthey like so the songs and/or push down the songs they do not like. Ingeneral, the more users who vote, the greater the ambiance of goodsongs. Thus, after step S1908, or in the case that the song is not over,the jukebox receives users' votes for particular songs in step S1910.Voting can be based on credits (as users buy credits), or tied to auser's account. In certain example embodiments, users must login toplace a vote, and in certain example embodiments, users can vote alimited number of times. Preferably, users may vote from at least twodistinct places within a location. The queue is updated based on thisvoting in step S1912, and the process returns to step S1902, where thedisplayed list is refreshed.

In certain example embodiments, the queue may be based on the totalnumber of votes for particular songs. In certain other exampleembodiments, users may vote for and/or against certain songs and the“net” information may be displayed, indicating the number for andagainst, or merely the net result. If there are more votes against asong than for, the system can perform one or more of the followingfunctions. For example, the jukebox simply may keep the song in thequeue with a negative number of votes. Alternatively, the jukebox maykeep the song in the queue with a zero or negative number of votes, but,for example, always wait until the net vote reaches at least 1 beforeplaying the song. Still alternatively, the jukebox may drop any songthat reaches zero or a negative number of votes.

FIG. 19B(1) is an exemplary screenshot showing a voting queue display.Display 1900 a shows the currently playing song 1902 and its progress1904. It will be appreciated that progress 1904 of currently play song1902 may be displayed in any number of ways, such as, for example, as anumber indicating the time remaining, a sliding bar, etc. Artist andsong list 1906 preferably is displayed based on the corresponding numberof votes in votes area 1908 a. Optionally, user area 1910 may indicateinformation about the users voting for the songs, such as, for example,the user placing the song on the list, the last user to vote for thesong, the name of the group “battling” to have the song played, etc.

FIG. 19B(2) is another exemplary screenshot showing a voting queuedisplay. FIG. 19B(2) is similar to FIG. 19B(1), but votes area 1908 breflects the “net” voting of users. That is, for example, in FIG.19B(1), the display indicates the number of votes for and against aparticular song, as well as the net voting result.

FIG. 19C is an exemplary block diagram showing a voting mechanism withina given location. Display 1900 a corresponds to FIG. 19B(1), though itwill be appreciated that a display corresponding to FIG. 19B(2) could besubstituted, as well as any other display indicating the same or similarinformation. The list preferably is updated by jukebox 16. Users mayvote to update the list (e.g. vote for/against a song) via jukebox 16,or by any device optionally connected to jukebox 16, such as, forexample, another jukebox 1912 a. a remote terminal 1912 b, a laptop 1912c, a PDA 1912 d, a cell phone 1912 e, another mobile device 1912 f, etc.

FIG. 19D is another exemplary block diagram showing a voting mechanismwithin a given location. FIG. 19D differs from FIG. 19C in that usersvoting from optionally connected devices 1912 a-f may affect the votinglist directly, without interfacing with jukebox 16.

An alternate application includes a voting-mechanism where multiplelocations (e.g. bars, restaurants, venues, etc.) are networked togetherthrough, for example, the Internet. Those linked locations allow morepatrons to “battle” against each other. In this embodiment, thenetworked jukeboxes would be playing the same song and collectively allusers from all locations would decide on the playing order through thevoting mechanism or the like. Thus, FIG. 19E is an exemplary blockdiagram showing a voting mechanism for use with multiple locations. Afirst jukebox 16(1) with a first plurality of mobile devices 1912a(1)-f(1) within a first location communicating therewith, as well as asecond jukebox 16(2) with a second plurality of mobile devices 1912a(2)-f(2) within a second location communicating therewith with a mayaffect a playlist accessible by jukeboxes 16(1) and 16(2).

FIG. 19F is another exemplary block diagram showing a voting mechanismfor use with multiple locations. It is like FIG. 19E, except firstplurality of mobile devices 1912 a(1)-f(1) and second plurality ofmobile devices 1912 a(2)-f(2) may directly affect the voting list.

An alternate application of this voting features relates to enhancingthe “pause” mode of a jukebox. A jukebox, while in pause mode, typicallyprevents users from selecting music from the jukebox. For example,bartenders may use a pause mode when a special event (e.g. a footballgame) is presented at the location and when the audio system of thelocation is playing the match or event. The voting feature can be usedto select which songs will be played after the special event is over. Ithas been widely observed that patrons watching a game very often leavethe location once a match is over. This alternate method of selectingsongs to be played is likely to motivate patrons to stay in a locationand/or continue using the jukebox, etc.

FIG. 20 is a flowchart showing an illustrative process for using auser-tailored system for managing music, communications, etc. inaccordance with one exemplary embodiment. It is to be appreciated thatthe Personal Music Assistant may work as a complement to, component of,etc. to systems according to this exemplary embodiment. In step S2000, auser accesses the user-tailored system, dubbed MyTouchTunes in thiscase. It is to be appreciated that a user may access the system at anumber of locations, such as, for example, via an Internet front-end, ata jukebox terminal, etc. It further is to be appreciated that the usermay access the system in any number of ways, such as, for example, byinputting a username and password combination into the Internetfront-end or jukebox terminal, by swiping a credit card at a jukeboxterminal, by scanning a site-specific “smart-card” or flash card, etc.In certain example embodiments, a user may be recognized throughbiometric data, such as, for example, finger prints, retinal scans, etc.It will be appreciated that biometric authentication may workindependently, or together with, more conventional forms of identifyingusers, such as, for example, username/password combinations,smart-cards, and the like. The system determines whether it recognizesthe user in step S2002. If the user is not recognized, the user can beprompted to create account/profile information, as in step S2004. Theaccount/profile information will be described in more detail below withreference to FIG. 21A.

If the user is recognized in step S2002, the MyTouchTunes main menu isdisplayed for the user in step S2006. From the MyTouchTunes main menu,users using a system according to this exemplary embodiment may, forexample, edit account/profile information in step S2010, manage music instep S2020, manage buddies in step S2030, communicate with others instep S2040, and/or access various value-added content that may beprovided by the system in step S2050. These and other features will bedescribed in more detail below with reference to FIGS. 21A through 21B.

FIG. 21A shows illustrative options available for editingaccount/profile information in one exemplary embodiment. As noted above,it is to be appreciated that the exemplary steps illustrated in FIG. 21Amay correspond to the steps required for initial account/profile setup.In such an initial setup case, however, an exemplary system mightrequire the user to complete all of the required information at one timebefore allowing the user to access the main menu (step S2006 in FIG.20). It also is to be appreciated that such account/profile informationcould be stored in various locations as necessary to a givenimplementation, such as, for example, in a central location or database,on a particular establishment's server, on specific jukebox terminals,and/or on a removable card that would identify the user and the user'sinformation when inserted into a jukebox.

A user would first input personal data in step 2012. Such personal datamay include, for example, an e-mail address for the user, a telephone(preferably mobile phone) number, and/or a name. The system also mayprompt the user to create a unique username and password so that thesystem can identify the user at later times and from other locations.Alternatively, the system may use the user's e-mail address as ausername and only require a corresponding password. Still alternatively,in the case of residential jukeboxes, for example, an exemplary systemmay not require a password at all. Based on the personal data, theexemplary system may gather enough information to recognize the user atlogins (e.g., online access, preferred location, other locations withina given area, etc.) as well as send e-mail and text messages to theuser. These exemplary features will be discussed in greater detailbelow.

In step S2014, users may specify various locations they frequent. Thisfeature may enable user-tracking by various establishments, advertisers,etc. Establishments may, for example, provide special offers to regularsor others in a particular area to entice them to come visit. Advertisersmay monitor the personal information, location information, andplaylists to provide, for example, concert tickets, special offers onCDs, t-shirts, and/or other merchandise that may seem to be appealingbased on the user's preferences. Still further, if such account/profileinformation is stored locally on various terminals, the system maycommunicate with those other terminals to provide the playlists inpreparation for a user's visit. In step S2016, a user may add creditsand/or specify payment information. Users may, for example, use theircredit cards to increase the number of credits they have before enteringan establishment, or while at an establishment. Alternatively, users maybecome “certified” by, for example, providing credit card informationand allowing jukeboxes to automatically bill their credit cards forfuture credits purchased, etc. It is to be appreciated that step S2016can be used to purchase credits for oneself or for someone else, suchas, for example, one's buddies, an employee of the establishment, etc.It also is to be appreciated that a user may transfer money from anaccount, such as, for example, a Pay-Pal account, to a jukebox-specificaccount, or a user might use such an account to purchase music and/orservices directly.

FIG. 21B shows illustrative options available for managing music in oneexemplary embodiment. In step S2022, a user may create or edit alreadyexisting playlists. Users preferably can search through songs using theabove-described methods and/or use system-generated suggestions to buildtheir playlists. Preferably, users also may give their playlistsdescriptive titles, such as, for example, “Favorite Jams,” “'80s Night,”“Smooth Love Songs,” etc. Users may further designate their playlists as“public” or “private” to allow or restrict other users from browsingtheir playlists. Users may, in step S2024, rate their songs and/orplaylists through the PickList feature. The PickList also may generate acustom playlist comprising the songs the user has rated the highest at agiven time. Alternatively, a PickList may comprise a list based on theHotHits list described above. In step S2026, a user may play music on ajukebox using, for example, any of the above described methods with orwithout using these playlists. Normally, selecting a playlist for playon a jukebox will add those songs to the regular queue. However, asdescribed above, users may pay an additional fee and/or use the biddingmechanism described above to play their music immediately. Furthermore,selecting a playlist (or playlists) for play on a jukebox normally willplay all songs in that particular playlist (or in those particularplaylists). However, users may unselect certain songs to prevent themfor being played. This enables users to further customize playlistsdynamically when they are playing their music.

FIG. 21C shows illustrative options available for managing buddy listsin one exemplary embodiment. Users may keep track of buddies (e.g.,friends, regulars at a bar, etc.). The system may use any instantmessaging standard, such as, for example, AOL Instant Messenger, MSNMessenger, Yahoo! Messenger, ICQ, a custom jukebox-specific protocol,etc. to send and receive messages. Preferably, the system would alertthe user of the buddies' statuses (e.g., online, inactive, busy, etc.).In step S2032, a user may create or edit an already existing buddy list.Users may search for buddies by, for example, inputting their names,e-mail addresses, etc. Additionally, users may invite friends to join byissuing invitations, preferably by e-mail or SMS (Short Message Service)text message to a mobile phone, in step S2038.

Users also may browse their buddies' music collections, playlists,PickLists, etc., as shown in step S2034. Users then could develop theirown playlists and/or PickLists based on what they perceive as popularamongst their friends. Users also may copy music from their buddies orsend music to their buddies, preferably for a fee, as shown in stepS2036. In a step not shown, users also may designate particular songs toplay when their friends log in to the jukebox, again, preferably for afee. Other features pertaining to communication between buddies will bedescribed below with reference to FIG. 21D.

FIG. 21D shows illustrative options available for communicating withothers in one exemplary embodiment. Preferably, the system can sende-mails and SMS messages to mobile phones. It is to be appreciated thatthe system should be able to communicate using any variety ofcommunications protocols, such as, for example, via e-mail and/ore-mail-like messages accessible only by the MyTouchTunes system. It alsois to be appreciated that bar managers may also send messages (e.g., viae-mail, SMS, etc.) to alert others of events, specials, etc. In stepS2042, users may check their inbox. Users may receive messages from, forexample, their friends (or buddies), proprietors, and/or advertisers,etc. Buddies may suggest, for example, songs or places to gather. Insome exemplary embodiment, buddies may receive instant messages on theirmobile phones alerting them of a get-together, a particular user'slocation in a bar, etc. Furthermore, users may leave messages for othersto appear on someone else's next log-in. Proprietors may send messagesto their regulars or others they wish to target to alert them, forexample, of drink specials, upcoming special events, etc. Advertisersmay, based on demographic information provided by users, extend specialoffers. In step S2044, users may send messages to others' e-mailaddress, MyTouchTunes inbox, mobile phones, etc. Alternatively or inaddition to step S2044, in step S2046, users may broadcast messages tobuddies or groups of others, to, for example, alert a particular groupof upcoming parties, etc. Thus, exemplary systems can learn aboutnetworks of friends through the messages that users send. In addition,the jukebox may directly provide an interface for the features describedabove, or it may provide for wireless access to the features, for thoseusers that may bring a wireless device with them to the location (orwithin range) of the jukebox. Some or all of the features can also beprovided to the users remotely by, for example, enabling users to accessthe jukebox services through the internet or other suitablecommunications network, using for example, the user's home computer.

FIG. 21E shows illustrative options available for accessing value-addedcontent in one exemplary embodiment. Users could access externalwebsites (preferably of partners) as shown in step S2052 for any numberof reasons. For example, advertisers may place banner ads pertaining tothe particular song or album selected to allow users to place orders forrelated merchandise. Advertisers may use profile information to targetads, e-mails, text, etc., potentially anywhere (e.g., online, on ajukebox, etc.). For example, jukebox use can be used as a “qualifier”for targeting certain products (either conspicuously ornon-conspicuously) to individuals who spend more than a certain amounton jukeboxes yearly. Users also may access external websites to link toa particular band's website, to order sheet music or guitar or bass“tabs,” to view lyrics, etc. Also, in step S2054, users may follow alink to download/purchase songs and/or albums from a third-partyprovider such as iTunes or Amazon.com. In some exemplary embodiments,this step may also be linked to from the “Manage Music” screen (stepS2020), etc. Additionally, in step S2056, users may order custom CDs andhave them shipped, preferably for a fee. Users could base these orderson their playlists, their PickLists, their buddies' playlists, theHotHits list described above, etc.

It is to be appreciated that although the above-described exemplaryMyTouchTunes system has been described in terms of a broad concept formaking accounts available on any compatible system, other exemplaryembodiments are contemplated where accounts may be made available tosmaller subsets of jukeboxes, including, for example, a single jukeboxterminal acting in isolation. Furthermore, a large group may act as ifit were one system in isolation, or, alternatively, it could havecomplete knowledge of all user accounts/profiles, locations, etc.

FIG. 22 is an exemplary screen shot of a login page in accordance withone exemplary embodiment. A user may enter an e-mail address in usernamearea 2200 and a password in password area 2202. As a shortcut, a usermay select a common e-mail domain from domain list 2204. It is to beappreciated that although this embodiment requires an e-mail address anda password, other embodiments may require a username that need not be ane-mail address. Similarly, it is to be appreciated that a username andpassword may not be required, for example, on a home jukebox system, andthat in yet further embodiments, only a username may be required. A usercan use keyboard 2206 to enter the required information, though it is tobe appreciated that other input devices, such as a keyboard attached toa home computer, may be used. It also is to be appreciated that thelogin screen shown in FIG. 22 may appear on an actual jukebox device, ona computer (e.g., through a web-interface, custom software, etc.), on amobile device, etc.

Preferably, a successful log-on displays a main menu for users. FIG. 23is an exemplary screen shot showing the features available after arecognized user has logged in, in accordance with one exemplaryembodiment. A customized greeting (e.g., the user's name) is displayedin area 2300. Playlists 2302, 2304, and 2306 are displayed withdescriptive names along with the number of credits required to play afull playlist. For example, to play playlist 2302 costs 7 plays.Preferably, playlists are presumed to be public, which allows otherusers to view them. Playlists may be designated private, however, as is,for example, playlist 2306. Users can create additional playlists bypressing playlist creator button 2308, and they can edit alreadyexisting playlists by pressing playlist manager button 2310. Theplaylist manager may allow users to, for example, change existingplaylists by adding and/or removing songs, deleting playlistscompletely, etc.

Users can manage a buddy list by adding a buddy by pressing add buddybutton 2314. Alternatively, they can remove a buddy by pressing removebuddy button 2316. Users also can communicate by sending messages totheir buddies by pressing send message button 2318. This feature can, incertain embodiments, for example, send SMS messages to mobile devices,send e-mails, send messages to appear when the recipient user nextlogs-in, etc. In still other embodiments, users can, for example, usethis feature to send songs, donate credits, etc. Indicator area 2320shows that the current user has received one message, and it identifiesthe sender. In other embodiments, however, other information may bedisplayed, a more complete inbox (e.g., with folders, forwarding, etc.)may be provided, etc. Credit indicator area 2322 provides accountstatus. In this embodiment, it indicates that the user has previouslypurchased 20 plays online, and has entered enough money in a localjukebox terminal for 5 additional plays, for a grand-total of 25potential plays.

Another aspect of the instant invention relating to improvements inbackground music will now be described. The local server and TuneCentral feature described herein, open up a whole new world forbackground music on a jukebox. Currently, when no paid for music isqueued, jukeboxes may play background (ambiance) music with the help ofan auxiliary system connected to the jukebox, such as DMX or satelliteradio. Alternatively, if they play background music with their ownmusic, they are limited to the songs available for play on the jukebox,typically about 2000 songs. These songs are also available for selectionby jukebox patrons. Conventional digital jukeboxes are typicallyconnected to a remote network through the internet for accessingextended music. These applications are therefore not well suited forproviding background music services other than the music locallyavailable as this would require constant download or streaming from theremote servers for the background music.

However, jukeboxes equipped with an external server or large musicpartition (such as Tune Central described herein) can select backgroundmusic to play from that large pool of songs, even if the song is notavailable for play through the standard interface. This permits a vastmusical variety for background music using jukeboxes. The backgroundmusic selection can be made automatically by the jukebox randomly orwith an advanced algorithm that selects music based on genres, themes,era or other criteria. Also, background music lists can be preprogrammedby a disk jockey or the like (background playlists) and sent from acentral server to jukeboxes. Since music rights can differ for songsavailable in pay-per-play mode and background music, there is, in anembodiment of the invention, an indicator for each song or songaggregations (e.g., all songs from ABC record label) allowing thejukebox to distinguish between songs that can be played as backgroundmusic (as opposed to normal jukebox play) based on the availability ofthe proper music rights, thereby enabling proper royalty accounting aswell. In an embodiment of the invention, the jukebox offers advancedoptions for allowing an operator to configure how background music willbe performed, based on genre, themes, indicators (flags), such asbillboard hit, Christmas music, playlists (e.g., DJ John—summer 2005),etc. In another embodiment of the invention, the operator configures thejukebox to allow the bartender to further configure the background musicmode through, for example, a remote control; much like the bartenderwould select a radio station in prior background music systems. Thismode offers genres or theme based music or playlists for enhancingbackground music functionality. The operator can, for example, configurewhich genre, theme or playlists is available to the bartender. Inaddition, a remote control with programmable keys combined with suitablesoftware can be provided to allow the bartender (or other person) toselect (e.g., for a particular zone) a certain background music playlist or TV audio input for special event like, for instance, a footballgame in a bar zone, thereby providing convenient and effectivebackground music services and other services through the jukebox device.

FIG. 24 is a flowchart showing an exemplary process for accessing asystem remotely according one exemplary embodiment. In step S2402, auser logs into a jukebox system from a location and/or device differentfrom a jukebox housed locally in a bar. In a preferred embodiment, theuser will access the system through a web browser to gain access to anInternet portal. However, it will be appreciated that other mechanismsfor accessing the system are possible, such as, for example, via amobile device (e.g. a cell phone, PDA, etc.), a stand-alone applicationto be run on a remote computer, an appropriately configured jukebox,etc. Moreover, it will be appreciated that the features and/or servicesoffered by the system may depend on the mechanism and/or device by whichit is accessed. For example, some features may be available for anillustrative embodiment that uses a web browser on a personal computerthat are not available over a cell phone, and vice versa. Keeping withthis example, but still for non-limiting exemplary purposes only,although an illustrative embodiment that uses a web browser on apersonal computer may have access to the full set of features and/orservices (e.g. music downloads, participation in forums, chat rooms,etc.), an illustrative embodiment that uses a cell phone may only beable to download music and receive text messages. Of course, as variousdevices become more interconnected and more powerful, it will beappreciated that such distinctions may no longer hold.

Step S2404 determines whether the user is recognized by the system as anexisting user. Users not recognized by the system preferably will beprompted to create an account, as in step S2408. Users may be requiredto supply, for example, their names, ages, e-mail addresses, etc.Preferably, users will be able to create profiles including, forexample, a name and/or nickname, their age, their location, and anassociated image. These profiles may be viewable by other users of thesystem. In some exemplary embodiments, users may be required to registerand/or create profiles before participating in some features of thesystem, for example. Alternatively, in other exemplary embodiments,users may specify that they want their information, or portions thereof,to remain private. A non-limiting exemplary screen shot for editingaccount information is provided in FIG. 26C, and an accompanyingdescription thereof is given below. After users create their account,preferably a central account database is updated in step S2410. In otherexemplary embodiments, a central account database need not bemaintained, and the account information may be stored elsewhere, suchas, for example, on jukeboxes, on a user's own personal computer, etc.

If users are recognized in step S2404, they may chose a feature and/orservice in step S2406, described in more detail in relation to FIGS. 25and 26A. In some exemplary embodiments, users may have their access tothe system limited by the service to which they subscribe. For example,in some example embodiments, users may have free and unlimited access tothe online system from personal computers, but may have to pay premiumsto access the services via PDAs. Thus, in a step not shown, even if anexisting user is recognized, if they attempt to access the system in anunauthorized way, they will not be permitted to access the system. Thisfeature may, in some exemplary embodiments, also may block unauthorizedaccess by users, registered or unregistered, who attempt toinappropriately access the system and/or its underlying code, songs,etc.

FIG. 25 is a flowchart showing an exemplary process for selecting one ormore of a non-limiting list of services and/or features in a systemaccording to one exemplary embodiment. Other features and/or services inaddition to, and in combination with, those described below are possibleand contemplated herein. FIG. 25 begins with step S2406 as discussedabove in connection with FIG. 24. It will be appreciated that in apreferred embodiment, the steps described below need not be selected inany specific order. For example, a user need not search for music beforecommunicating with other users. It also will be appreciated that thesteps described below may, in some exemplary embodiments, be performedalone or in combination. For example, a user may wish to search formusic before communicating with other users.

In step S2502, a user may search for music. Preferably, a user mayspecify search fields, alone or in combination, such as, for example,artist, song, album, genre, etc. An exemplary screen shot showing theresults of a search is provided in FIG. 26E and is discussed below.After searching for music, a user may then, for example, add the foundsongs to a playlist, purchase the songs, or recommend the songs toothers. For example, a typical use might include a user remembering acatchy song at a bar but only remembering that it was a reggae song thathad something to do with “Zion” from Damien Marley's latest album.Accordingly, a user might, in step S2502, search with the followingparameters: artist, “Damien Marley”; song, “Zion” and genre, “reggae.”After the search is performed, the user would be able to select “Road toZion” from a results list. After finding the song, the user might add itto a playlist for convenience the next time the user visits a bar, andthe user might recommend the songs to friends. A user might alsopurchase the single and/or download a digital copy. A particularly bolduser might order the entire “Welcome to Jamrock” album.

In step S2504, a user may manage the user's playlists. An exemplaryscreen shot showing how a user might manage playlists is provided inFIG. 26D and is discussed below. Briefly, a user may, for example,create a new playlist, delete an existing playlist, and/or edit anexisting playlist. In a preferred embodiment, a user might also share aplaylist, for example, with friends or the public, and a user might alsosearch for publicly available playlists. Preferably, a playlist willhave a unique name (e.g. “Joe's All-Time Favorites,” “Ghetto Grooves,”“Maximum Chill-Out,” etc.), and, preferably, a playlist will have aplurality of songs associated therewith. It will be appreciated that aplaylist might contain only one song. Additionally, it will beappreciated that in some embodiments users, professional DJs, or othersmay create and sell playlists, and that users could pay for and downloadsuch playlists through the system.

A user may purchase music in step S2506. In one exemplary embodiment, auser may order a single song, a plurality of songs, an entire album, ormultiple albums. In some exemplary embodiments, a user may have hisorder shipped, while in other exemplary embodiments licensed digitalcopies may be made available. In still other exemplary embodiments, itmay be possible to purchase music and download it directly to a mediaplayback device (e.g. an appropriately configured PDA, cell phone, orthe like).

Preferably, a user could communicate with others via e-mail and/or textmessages in step S2508. Step S2508 preferably also will allow users toparticipate in online forums and live chat rooms. Messages sent throughthis step may be delivered to conventional e-mail inboxes, cell phones,etc. Additionally, messages may be displayed on jukeboxes, for example,when recipient users initially log-in, when messages are sent and/orreceived, etc. It will be appreciated that online forums and chat roomsmay use protocols, such as, for example, newsgroups, Network NewsTransfer Protocol (NNTP), Usenet, Internet Relay Chat (IRC), etc., orthey may use custom protocols.

From time-to-time, proprietors or the managers of the system may sponsorcontests, promotions, or giveaways. Users may participate in suchactivities through step S2510. For example, a proprietor might allowanyone who prints a coupon to avoid a cover charge. As another example,there might be a competition for the best playlist. It will beappreciated that these example promotions are for illustrative purposesonly, and that other contests, promotions, giveaways, or the like may bepossible.

In step S2512, a user may edit that user's profile. The discussions ofstep S2408 from FIG. 24 above and FIG. 26C below provide additionaldetail on the type of information preferably associated with a userprofile. A user may logout of the system in step S2514. In someexemplary embodiments, a user may be logged out of the systemautomatically after a predefined period of inactivity.

FIGS. 26A through 26E, which provide sample screen shots, are forexemplary, illustrative purposes only. The specific fields, buttons,graphics, etc. and locations of the same are in no way intended to belimiting. On the contrary, FIGS. 26A through 26E present only onepreferred embodiment of the instant invention. It will be appreciatedthat other arrangements and combinations are possible, and thosearrangements and combinations are contemplated herein. It also will beappreciated that a user may navigate through the following screens inany number of ways, and the use of the term “press” indicates only onesuch implementation. For example, a user may navigate the screens with amouse, keyboard, touch screen, stylus pen, etc. Preferably, the userinterface will be very smooth and streamlined with a limited amount ofadvertising or other non-core material. Accordingly, whenadvertisements, surveys, and the like are accessible through the userinterface, they preferably will be linked to jukebox functions and orperks tied to their links. For example, an advertiser may reward usersclicking on one of its advertisements with credits, free plays, entriesin competitions, etc. Similar rewards may be given to usersparticipating in surveys.

FIG. 26A is an exemplary screen shot showing the features availablebefore a user logins into a system according one exemplary embodiment. Auser will log into the system by entering a username and password intousername field 2600 and password field 2602, respectively, and thenpressing login button 2604. Alternatively, an unregistered user maycreate an account by pressing register button 2606. Navigation buttons2608 help the user navigate the system quickly. In this exemplaryembodiment, navigation buttons 2608 include a home button, an aboutbutton, a FAQ button, and a Find a juke button. The home button returnsthe user to an introductory screen. The about button preferably displaysinformation about the system, including, for example, helpdocumentation, terms and conditions of use, etc. The FAQ buttonpreferably provides information complementary to that given by the aboutbutton and is customized to provide information regarding the mostfrequently asked questions about the system and its associated servicesand features.

The Find a juke button preferably enables a user to search for alocation with a jukebox. Users may, for example, search for locationsnear a certain address, in a particular city to which the user may betraveling, locations that offer special features (e.g. drink specials,guest DJs, etc.), locations likely to play music the user likes (e.g. abar with line dancing might be appropriate for a country music fan,etc.), etc. Social networks also may be built based on postal codes,schools (e.g. high schools, colleges, universities, etc), etc. In apreferred embodiment, when a user finds a specific location, the usermay have custom information, for example, directions, custom maps, hoursof operation, parking information, etc. displayed. It will beappreciated that because jukeboxes located at many locations preferablyare connected to the system and that users' playlists preferably areaccessible by the system, users may receive recommendations likely tofit their tastes. For example, the system might suggest a specific barto users of a certain age in the same town who are known to like aspecific type of music. In certain example embodiments, the jukebox canrecommend that users form certain connections. These suggestedconnections between patrons (and thus potential “buddies”) preferablymay be based on information known to the jukebox though not necessarilyknown to other users. Such information can include, for example, venuesfrequented, musical tastes, ages, etc. In certain example embodiments,therefore, users may be connected based on where they go, notnecessarily where they are from.

Users may enter search terms in search field 2610. Additionally, usersmay further limit their searches by searching only in one of thecategories listed in search parameters list 2612. It will be appreciatedthat the fields of search parameters 2612 are for illustrative purposesonly—other fields may be present in addition to, or in place of, thoselisted, such as, for example, year, popularity, etc. A user may conductthe search by pressing search button 2614. Users may alternativelysearch by filling in search field 2616 and selecting a search parameterfrom the list of search parameters in search parameters dropdown list2618. The results of a search may be displayed according to FIG. 26E,discussed below.

A non-limiting exemplary list of genres is given in genre list 2620. Itwill be appreciated that other genres may be present in genre list 2620,and it also will be appreciated that, in this exemplary embodiment,additional genres may be accessed by clicking the “More . . . ” buttonin genre list 2620. A user pressing a specific genre may receive contenttailored to that genre. For example, pressing the “Alternative” genremay, for example, present a list of the most popular alternative albums,a list of forums dedicated to the discussion of alternative music, etc.

Most popular albums list 2622 contains information related to the mostpopular albums and preferably displays the album cover, the artist name,and the name of the album. Most popular album list 2622 may be generatedin any number of ways. For example, Most popular album list 2622 may bebased on preferences of users of the system, commercial data regardingalbum sales, album sales within a particular geographic segment, etc.Preferably, most popular album list 2622 may be changed depending on thegenre selected from genre list 2620.

Users may access community-specific content by selecting a specificcommunications method from communications methods 2624. In thisexemplary embodiment, users may communicate in groups and/or forums. Itwill be appreciated that participation in groups and/or forums mayrequire registration, and that groups and/or forums may be designatedpublic or private. Preferably, groups will comprise users, for example,with similar interests, in near locations, etc. For example, there maybe a group for so-called “Dead Heads” to allow them to plan meet-uppoints, transportation, etc. for upcoming tours of the Grateful Dead.Forums may function similarly, though they preferably will be morestatic, allowing threaded messages between users.

Breadcrumbs trail 2626 provides a convenient way for navigating throughthe system. Specifically, breadcrumbs trail 2626 traces the path a usertakes in accessing a certain page. Pressing a specific part ofbreadcrumb from breadcrumbs trail 2626 preferably takes the user to acorresponding location.

Information area 2628 and information area 2630 may be customized toprovide additional information to the users. In this exemplaryembodiment, information area 2628 suggests reasons for using specificfeatures (here, creating custom playlists), and information area 2630provides useful tips (here, relating to how to create a customplaylist). It will be appreciated that information areas 2628 and 2630may change depending on, for example, the user, the time of access, thenumber of times a user has accessed a given page, etc. Furthermore, itwill be appreciated that information areas 2628 and 2630 may containdifferent information not related to use of the system, such as, forexample, advertisements, promotions, etc.

FIG. 26B is an exemplary screen shot showing the features availableafter a user logins into a system according to one exemplary embodiment.Based on the user's profile information, user information 2632 and usericon 2634 may be displayed. In this exemplary embodiment, userinformation 2632 comprises a username and a location, and user icon 2634is a solid square. It will be appreciated that additional and/oralternate information may be displayed, and it also will be appreciatedthat only information provided by users may be displayed. Users may edittheir profile, including user information 2632 and user icon 2634 bypressing edit profile button 2636. Users may log out of the system bypressing logout button 2638. In some exemplary embodiments, users may belogged out automatically after a predefined period of inactivity haselapsed.

User playlists 2640 displays the playlists the user has created and/orimported. It will be appreciated that user playlists 2640 will be emptyif a user has not created or imported any playlists. Preferably, theexemplary embodiment will display the unique name specified by the userfor each of the playlists. Users may expand one or more specificplaylists from user playlists 2640 to show the songs associated with theplaylist. In the example shown in FIG. 26B, the “Alternative” playlistis expanded, and four songs 2642 are shown as being associated with the“Alternative” playlist. It will be appreciated that users may expandmultiple playlists, and/or collapse lists after they are expanded.

Preferably, the system will display at least one recommendation 2644.The recommendation preferably will include an album cover, a song name,artist information, and keywords associated therewith. Therecommendation preferably will be generated automatically, and may bebased on a variety of data. The data for generating a recommendation mayinclude, for example, user demographic data (e.g. age, gender, race,etc.), the number and types of songs in the user's playlists, songs theuser has purchased through the system, popular songs, etc. Preferably,the system will allow the user to quickly add the recommended song to aplaylist by pressing add button 2646.

FIG. 26C is an exemplary screen shot showing how a user might updateaccount information. Stats box 2648 displays basic information that willbe publicly available. In this exemplary embodiment, it includes ausername, real name, gender, location, and age. However, it will beappreciated that other embodiments may require additional and/oralternate information. It also will be appreciated that users may electto keep some information (e.g. real name, age, etc.) private.

The username selected in the initial account setup is displayed asusername field 2670. Preferably, a user will not be able to changeusername field 2670 after initial setup, and, preferably, each usernamewill be unique. The user may enter an e-mail address in e-mail addressfield 2652. In a preferred embodiment, the system will send importante-mails (e.g. terms and conditions information, notices of giveaways,bills, etc.) to this e-mail address. A real name may be specified inname field 2654. Although this exemplary embodiment shows name field2654 as a single field, it will be appreciated that multiple fields mayinstead capture the same information (e.g. fields for first and lastnames; first, middle, and last names; etc.). A user may choose a genderfrom gender options 2656.

A location may be specified in location field 2658. Although thisexemplary embodiment shows location field 2658 as a single field, itwill be appreciated that multiple fields may instead capture the same oradditional information (e.g. fields for city and state; city, state, andzip code; city, province, and country; etc.). A date of birth may bespecified in date of birth field 2660. Although this exemplaryembodiment shows date of birth field 2660 as three fields, it will beappreciated that a single field or multiple fields in a different ordermay instead capture the same or additional information (e.g. one fieldfor month, date, and year; month and year only; month, date, and year;etc.).

A user may enter personal or other information in free-form biographyfield 2662. Additionally, a user may specify a signature line or tagline in forum signature field 2662. Preferably, the system wouldautomatically append the contents of forum signature field 2662 tousers' posts to groups and/or forums. A user may upload a picture oricon by entering a file location in picture field 2666. Preferably, thispicture would be displayed on login and/or when a user posts a messageto a group or forum.

In a preferred embodiment, required fields may be, for example, markedwith an asterisk (*), highlighted, or otherwise designated. In otherembodiments, a user may additionally store purchase information, suchas, for example, credit card information, billing and shippingaddresses, etc. This information could be used, for example, if usersdecide to order or download songs, albums, or other merchandise, toautomatically debit an account so that users could “play now and paylater” while using jukeboxes in bars and/or clubs, etc.

Playlist manager button 2668 provides quick access to the playlistmanager form, discussed in more detail below in connection with FIG.26D. Collapse and expand buttons 2670 allow a user to quickly change theplaylist information showing on the far left of the display in thisexemplary embodiment. Recommendations 2672 preferably are generated inthe manner described above, and clicking one or more recommendationpreferably allows a user to associate them with their own playlistsquickly and easily.

FIG. 26D is an exemplary screen shot showing how a user might manageplaylists. In this exemplary embodiment, a user's custom playlists aredisplayed horizontally (as playlist labels 2674), and their respectivecontents are displayed underneath the appropriate headings (as playlistcontents 2676). It will be appreciated, of course, that alternatearrangements are possible. Preferably, each playlist has a uniquedescription associated therewith, and each entry in the playlistdisplays the number of the song in the playlist, the name of the song,and the artist. Users preferably may edit playlists by “dragging” and“dropping” songs into and/or out of a playlist. Users may use the searchfunction to add a specific song. In some embodiments, removing all ofthe songs from a given playlist cause the user to be notified that theplaylist is empty, and asks the user whether the playlist should bedeleted.

A user may create a new playlist by pressing create new playlist button2678. Preferably, the user will be prompted to enter a unique name forthe new playlist. Then the user may edit the playlist in theabove-described manner. Users also may share playlists by pressingsharing button 2680. Sharing button 2680 allows users to designate theirplaylists as public to allow other users to retrieve their contents,preferably allowing users to drag and drop selected playlists intocategories, such as, for example, public, private, etc. Correspondingly,users may search for playlists created by other users, prepared by DJs,etc. and then copy and/or import the playlist. Users may deleteplaylists by pressing delete playlist button 2682 to display list ofplaylists 2684 and then selecting the playlist to delete from the listof playlists 2684.

FIG. 26E is an exemplary screen shot showing the results of anillustrative search for music. In this exemplary embodiment, ahypothetical user searched for “portis*”, where the asterisk (*)indicates a wildcard. Preferably, search results will be grouped byartist (artist list 2686), track/song (track/song list 2688), and/oralbum (album list 2690). Preferably, each result within a grouping mayhave a rank 2692 associated therewith. This rank may be based on, forexample, the number of users with the artist/track/album in a playlist,the current position on the Billboard (or other) charts, all-time sales,etc. Additionally, in a preferred embodiment, users may be able to sortthe results within a category alphabetically or by rank to facilitatethe location of a specific result. Because users' attention spans arefinite and because of space limitations, the output of the searchpreferably will be limited to a few (preferably at least five andpreferably no more than ten) results, while more button 2694 will allowthe user to browse an expanded list.

FIG. 27 shows an exemplary system for downloading music to a mobiledevice. A user indicates via mobile device 2702 that the user isinterested in downloading a song or songs after logging into jukebox2703. It will be appreciated that many types of mobile devices 2702 maycommunicate with jukebox 2703 over many different communicationsnetworks. For example, an appropriately configured cell phone maycommunicate over the data channel of a cell network, a PDA maycommunicate over standard TCP/IP, etc. Jukebox 2703 communicates over anetwork 2704 to interface with music repository 2706. Preferably, musicrepository 2706 will contain a broad range of potential downloads. Forsome requests, it may be necessary to confirm the download if, forexample, there are multiple possible version of a song (e.g. VanMorrison and Jimmy Buffett both have versions of “Brown Eyed Girl,”etc.), or for confirmation purposes. After music repository 2706receives a request, it will select the appropriate song (or songs) andsend it back through network 2704 to mobile device 2702.

Although not reflected in FIG. 27, alternate embodiments may send anappropriate song to another designated device. For example, a user at abar might hear a song and want it to be sent to his home computer. Usersin a car might want the song to be available the next time they visit aparticular bar, and thus, for example, the song may be downloaded to aremote jukebox. In some exemplary embodiments, appropriate song 2708 maybe sent through a different communications network, as appropriate.

Users may be billed according to billing information they inputted. Forexample, a stored credit card may be charged whenever a song isdownloaded via the jukebox interface. As another example, a user maysetup a special jukebox-specific account, linked to, for example, aPay-Pal account. In a related aspect, users may use their cell phones(or other suitable portable devices) to purchase media, register withthe jukebox, etc. by exchanging codes (e.g. via SMS messages) with thejukebox. For example, a user may first identify himself or herself withthe jukebox (e.g. may login on the jukebox or remotely through a mobiledevice). Depending on whether the user's cell phone number (or e-mailaddress, etc., depending on the implementation), the user may have toenter the appropriate information. An SMS (or appropriately similar)authorization message and/or code may be sent to the user. The user maythen enter that code on the jukebox to begin purchasing music, creatingpersonalized content, accessing features available to recognized users,etc. This method of communication also may in some example embodimentsenable users to pre-verify and/or pre-pay for music purchases remotely.

FIG. 28 is a flowchart showing an exemplary process for retrievingmusic. A user might hear a song being played, for example, at a bar, ina club, on the radio, etc., as in step S2802. A user typically decidesto purchase a song in step S2804 after hearing it. However, it will beappreciated that a user might choose to download a song without hearingit because, for example, the user's friends recommended it, the userdownloads all of the songs by a particular artist, etc.

Using a mobile device, the user logs into the jukebox system in stepS2806 and selects the song to purchase in step S2808. The use of amobile device allows for quick and convenient “impulse” purchases. Insome embodiments, the choice of what song to purchase might beautomated, for example, by selecting the song currently playing at agiven location, the song currently playing on a certain radio station,the song just played at a given location, etc. The user may specifypurchase parameters in step S2810, such as, for example, how to pay forthe song, the device to which it should be downloaded, etc. In stepS2812, the song is delivered to the user via the jukebox interface. Itwill be appreciated that the song may be delivered to other devices,such as, for example, a particular jukebox, a portable media device, alaptop, a home computer, etc.

FIG. 29 is a block diagram of an improved downloading digital jukeboxsystem with remote devices accessing a jukebox from within a particularlocation. A jukebox 16 is located within a particular location, bar, orthe like. Users may access jukebox 16 through user interface 24 runningthereon. However, users also may access jukebox 16 remotely. Thus, aplurality of mobile devices 26 a-26 d are shown located in theparticular location. Mobile devices 26 a-26 d are, respectively, alaptop, a PDA, a cell phone, and other personal devices, though it willbe appreciated that other properly configured devices may be used. Eachmobile device 26 a-26 d is equipped with a wireless transmitter 27 a-27d, respectively. Mobile devices 26 a-26 d preferably allow registeredusers to effectively logon to jukebox devices and access specificcontent, such as, for example, customized playlists, personalizedscreens, messages from other recognized users, etc. Preferably, a changemade by one of the mobile devices 26 a-26 d (e.g. to user settings,playlist setup, etc.) will be reflected by all of the mobile devices 26a-26 d. For example, if a user creates a new playlist, edits an existingplaylist, changes a password, etc. on a jukebox via user interface 24,user interfaces 24 a-24 f will reflect that change.

Mobile devices 26 a-26 d may communicate through an external network tocommunicate with jukebox 16 having communicator 25. It will beappreciated that mobile devices 26 a-26 d may communicate over a LAN,wireless Internet, Bluetooth, or any other suitable communicationsnetwork.

Preferably a central database of recognized user information ismaintained and accessible by each of the jukebox devices 16, 16 a-f andremote devices 26 a-d. However, in some exemplary embodiments, localdatabases of recognized user information may be maintained on devices.Preferably, the devices will communicate with each other through acommunications network, such as, for example, the Internet. However, itwill be appreciated that other communications methods are possible, suchas, for example, through wired communications over a LAN, wirelesscommunications, etc.

FIGS. 29A-29E provide additional, non-limiting exemplary configurationsthat remotely access jukeboxes. It will be appreciated that othervariations on and combinations of these exemplary configurations arepossible and contemplated herein.

FIG. 29A is a block diagram of an improved downloading digital jukeboxsystem with remote devices accessing a jukebox from within a particularlocation. In this exemplary embodiment, jukebox 16 and the plurality ofremote devices are located within a particular location. Jukebox 16includes a user interface 24 that allows jukebox users to, for example,make selections, create profiles, edit playlists, etc. Jukebox 16 alsoincludes a wireless communications device 25. Remote devices 26 a-26 bcommunicate with jukebox 16 through their respective wirelesscommunication devices 27 a-c. In this example embodiment, remote devices27 a-c are, respectively, a laptop, a PDA, and a cell phone. It will beappreciated that other remote devices may communicate with jukebox 16.It also will be appreciated that remote devices according to this systemmay operably communicate with jukebox 16 from outside the particularlocation, with the range being determined by the hardware on jukebox 16and remote devices 27 a-c and the protocols over which they communicate.Thus, for example, wireless communications over 802.11g connections mayallow for users to access jukebox 16 from within a location, tablessetup outside the location, and other areas immediately surrounding thearea.

Remote devices 26 a-c allow users to login to jukebox 16 remotely,without having to access jukebox 16 and user interface 24 directly.Thus, a user can, for example, play songs, edit playlists, and performother jukebox-related activities without using user interface 24directly. It will be appreciated that remote devices 27 a-c may havetheir own user interfaces, which may be the same as or different fromuser interface 24. User profile information may be stored locally onjukebox 16, on a remote server (not pictured), or on a remote device 27.Preferably, a change made by a remote device (e.g. to user profileinformation, playlist contents, purchased media, etc.) would be mirroredon jukebox 16, any other associated remote devices, and/or on otherjukeboxes, etc.

FIG. 29B is a block diagram of an improved downloading digital jukeboxsystem with remote devices outside of a particular location accessingthe digital jukebox system. In this exemplary embodiment, jukebox 16with local server 22 and user interface 24 is connected to a network 14.Unlike remote devices 26 a-26 c which connect directly with jukebox 16in FIG. 29A, these remote devices 26 a-26 c also are connected tonetwork 14. Thus, users may login to jukebox 16 over a potentially broadarea. For example, remote devices 26 a-26 c may connect with jukebox 16over LAN, WAN, Internet connection, or the like. User profileinformation may be stored on local server 22. Again, preferably, achange made by a remote device (e.g. to user profile information,playlist contents, purchased media, etc.) would be mirrored on jukebox16, any other associated remote devices, and/or on other jukeboxes, etc.

FIG. 29C is another block diagram of an improved downloading digitaljukebox system with remote devices outside of a particular locationaccessing the digital jukebox system. FIG. 29C is like FIG. 29B, in thata plurality of remote devices 26 a-26 c are connected to jukebox 16 overnetwork 14. However, FIG. 29C includes a database 29 connected tonetwork 14. Database 29 may store, for example, user profileinformation, users' playlist definitions, etc. This configuration may beadvantageous in some exemplary implementations because a plurality ofjukeboxes connected to network 14 may all access the central database 29without contacting individual jukeboxes or individual remote devices,which may not always be available.

FIG. 29D is a block diagram of an improved downloading digital jukeboxsystem with another downloading digital jukebox system outside of aparticular location accessing the first digital jukebox system. In thisexemplary embodiment, a jukebox 16 a with a local server 22 a and a userinterface 24 a are located within a first location, and a jukebox 16 bwith a local server 22 b and a user interface 24 b are located within asecond location. It will be appreciated that the locations may bedifferent rooms within a single bar, two separate establishments, etc.Both jukebox 16 a and jukebox 16 b are connected via network 14. Userprofile information may be stored at one or both of local server 22 aand 22 b. In some exemplary embodiments, if user profile information isstored on only one local server, a user logging-in to one jukeboxpreferably would be able to access information stored on the other localserver. In other exemplary embodiments, if user profile information isstored on both local servers, preferably any changes made on one jukeboxwould be mirrored on the other. In still other exemplary embodiments,user profile information may be retrieved from a first jukebox andstored to a second jukebox only when a user accessed the second jukebox.These configuration are advantageous because they do not distribute userinformation to areas where users do not access their information. Forexample, a user who travels from Washington to Los Angeles on businesswould be able to access that user's particular information created inWashington by logging-in to a jukebox in Los Angeles; however, becausethat hypothetical user has not logged-in to a jukebox in Montreal,jukeboxes there would not necessarily have the user's information storedlocally.

FIG. 29E is another block diagram of an improved downloading digitaljukebox system with another downloading digital jukebox system outsideof a particular location accessing the first digital jukebox system.FIG. 29E is like FIG. 29D, in that a jukebox 16 a is connected to ajukebox 16 b over network 14. However, FIG. 29E includes a database 29connected to network 14. Database 29 may store, for example, userprofile information, users' playlist definitions, etc. Thisconfiguration may be advantageous in some exemplary implementationsbecause a plurality of jukeboxes connected to network 14 may all accessthe central database 29 without contacting individual jukeboxes orindividual remote devices, which may not always be available. It will beappreciated that a plurality of jukeboxes may be attached throughnetwork 14.

FIG. 30 is an exemplary flowchart showing one way in which users maychange their status by becoming “verified users.” In step S3002, apotential user creates a jukebox account to become a registered user. Asdescribed above, the potential user may create the account on a jukeboxat a location, or by remotely accessing a jukebox by, for example, usinga personal computer, laptop, mobile device, etc. It will be appreciatedthat potential users who unexpectedly or spontaneously walk in on aget-together for verified users may wish to become verified usersimmediately and create their account with little or no prior planningRegistered users receive notifications of get-togethers, special events,and the like in step S3004. Such notifications may be sent via e-mail,SMS text message, through a message displayed when a registered userlogs onto a jukebox locally, etc. In certain preferred embodiments,registered users will be informed of get-togethers only if they meetpredefined qualifications. For example, all registered users living inthe Boroughs of New York may receive a notice of a get-together inManhattan, but a registered user in Des Moines may not. As anotherexample, users who specified they like Metal Music may not receivenotices of Go-Go get-togetheres.

After a registered user receives a notification regarding aget-together, the registered user may participate in that event, as instep S3006. This step might involve attending a bar, event, socialevent, or the like. In step S3008, the registered user becomes averified user. This step might require the user to log onto a jukeboxduring the get-together. Alternatively, registered users might receivevouchers, codes, or the like to later enter into a jukebox (locally orremotely) to change their status to verified. In certain otherembodiments, registered users may drop their business cards, sign lists,or otherwise indicate their presence to have their status changed forthem. Thus, In step S3010, a user may have privileges granted, accessrights changed, etc. based on verified status. For example, a verifieduser may be gain access to certain groups/discussion forums for verifiedusers only. Verified users also may, in certain exemplary embodiments,make un-moderated postings. In certain other exemplary embodiments,verified users may be able to access special promotions not available toother users.

FIG. 31 is an exemplary flowchart showing how registered users mayreceive credits for referring potential users. In step S3102, a userlogs onto a jukebox (either locally or remotely). In step S3104, usersspecify some contact information for potential future users. It will beappreciated that step S3104 may be accessed when users create newaccounts, when registered users access a form, etc. It also will beappreciated that contact information may be used, as appropriate, tosend, for example, an e-mail, a text message, conventional mail, etc. Instep S3106, invitations are sent to potential future users by thejukebox using the provided contact information. Lastly, in step S3108,referring users may receive credits. In certain example embodiments,credits may be awarded based on the number of users referred. In certainexample embodiments, credits may be awarded based on a formula (e.g. 1credit for every five users referred and/or registered), which mightinclude bonuses (e.g. a bonus may be given when 10, 25, and/or 50referred users become registered users).

FIG. 32 is an exemplary flowchart showing how registered uses mayreceive credits for creating public playlists. In step S3202, a userlogs onto a jukebox, either locally or remotely. In step S3204, a usercreates a public playlist. As described above, a user will associatecertain instances of media with a playlist, preferably giving the entireplaylist a descriptive name. It will be appreciated that users maycreate playlists using any of the methods described above, including,for example, drag-and-drop features, search features, etc. In certainexemplary embodiments, it may be necessary to designate playlists aspublic.

In step 3206, jukebox users may access public playlists and songs aspart of their normal jukebox activities. The jukebox monitors useractivity, especially with respect to the songs and playlists accessed.In certain exemplary embodiments, the jukebox will maintain counts,percentages, and the like related to the songs and playlists accessed.The jukebox will reward users based on the accessions of other users instep S3210. For example, users may be rewarded if their playlist(s)is/are accessed the most of any playlist, is/are accessed above acertain threshold number of times, is/are selected more than otherplaylists in a predefined category, etc. In certain exemplaryembodiments, users may be rewarded based on the contents of theirplaylists. For example, users may be rewarded based on whether theirplaylists contain a predefined number and/or proportion of the mostpopular songs, as determined by the jukebox. It will be appreciated thatusers may be rewarded in any number of ways. For example, one obviousway users may be rewarded is by giving them credits for additional playson the jukebox. Users also may be rewarded by being entered in certainpromotions, giveaways, or the like.

The present disclosure has used certain terms that should not beinterpreted as limiting the invention to a particular embodiment,hardware components and configurations, software configurations, etc.For example, many features and examples have been described in relationto their existence within a bar, pub, or other environment. However, itwill be appreciated that the features present in the exemplaryembodiments of the present invention are adaptable for use in anylocation where a jukebox (or multiple jukeboxes) may be located.Similarly, while certain features and functions are described withreference to usage by “users,” “owners,” “operators,” “patrons,” etc.,it will be appreciated that these terms are generic and may, in mostcases, be used interchangeably depending on the embodiment chosen andthe feature employed. For example, while it may be advantageous to limitthe initial song selection to owners and/or operators, in certainexemplary embodiments, patrons may play a role in the initial songselection.

Still further, particular hardware combinations and configurations aredisclosed which represent only one way which the embodiments may beconstructed. Central servers may, in some exemplary embodiments, becomprised of one or more servers acting together or separately tocoherently provide the full range of services necessary to enable afunctioning jukebox. For example, a cluster of servers may comprise avirtual central server, with one server providing media, anothertracking membership, still another processing licensing, etc.

Similarly, the local servers described herein may be incorporated intothe jukeboxes. For example, the local servers may appear to functionindependently, even though they exist as part (e.g. partition) of anintegrated mass storage device within the jukebox. Indeed, as hard disksbecome larger and less expensive, they may preferably serve thefunctions of local servers. One presently preferred embodiment comprisesa 120 GB hard drive containing 25,000 songs as the factory drive.However, flash media or any storage media now known or later developed(or combinations thereof) may be used as the factory drive, expandedmedia storage or local server, depending on the desires of a systemdesigner for a particular jukebox application. In other words, theinvention is not limited to any particular storage technology orconfiguration, but instead can be implemented using any suitable storagetechnology.

Also, although the term “song” has been used sometimes in theabove-description, this term is not intended to be limiting to the scopeof the invention, and any instance or instances of media (e.g., song,video, song/video combination, data, information etc.) can be used inany embodiment herein and still fall within the intended scope of theinvention.

Lastly, it will be appreciated that the screen shots and softwarearrangements presented herein are only one preferred method fororganizing and displaying the features disclosed herein. Otherconfigurations are possible and are therefore contemplated herein.

While the preferred aspects of the invention have been illustrated anddescribed herein, it will be apparent to one of ordinary skill in theart that various changes and/or modifications can be made. Thus, thespecific description herein is meant to be exemplary only and is notintended to limit the invention beyond the terms of appended claims.

What is claimed is:
 1. A system operable to facilitate the playback ofmusic from a catalog of playable songs in an out-of-home pay-for-playestablishment, the system comprising: at least one processor; and amemory coupled to the at least one processor, the memory comprisinginstructions that, when executed by the at least one processor, causethe at least one processor to at least: enable a plurality of registeredusers to execute respective login operations via respective mobiledevices to indicate that the respective users are present at theout-of-home pay-for-play establishment; in response to a first logged-inregistered user selecting a song, add the selected song to a queue ofsongs to be played back at the out-of-home pay-for-play establishment,at least a portion of the queue being displayable for the registeredusers; receive, from a second logged-in registered user via the mobiledevice of the second logged-in registered user, a vote on one or more ofthe songs in the displayable portion of the queue; and cause songs fromthe queue to be played at the out-of-home pay-for-play establishment,wherein the portion of the queue and corresponding tallied votes forsongs in the portion of the queue are viewable via the mobile devicesthat the logged-in registered users used to execute their respectivelogin operations, and wherein songs are selectable from a plurality ofpredefined playlists accessible to users, the predefined playlistsincluding at least one of each of: a playlist generated by a registereduser, a playlist of songs popular at the out-of-home pay-for-playestablishment, and a playlist of songs known to be liked by a logged-inregistered user making a selection.
 2. The system of claim 1, whereinthe addition of the selected song to the queue of songs to be playedback at the out-of-home pay-for-play establishment is conditioned oncollection of a predefined non-zero number of credits.
 3. The system ofclaim 1, wherein the votes can be either votes for or votes against asong.
 4. The system of claim 3, wherein the memory comprises furtherinstructions that, when executed by the at least one processor, causethe at least one processor to at least: tally the votes for and thevotes against each song in the queue; and cause a display of the talliedvotes for and the tallied against each song in at least the portion ofthe queue.
 5. The system of claim 1, wherein each said predefinedplaylist has an associated playlist identifier that identifies therespective predefined playlist.
 6. The system of claim 5, whereinplaylist identifiers are playlist names.
 7. The system of claim 1,wherein an identifier of the user who selected the currently playingsong is viewable via the mobile devices that the logged-in registeredusers used to execute their respective login operations.
 8. The systemof claim 1, wherein an identifier of the user who voted for thecurrently playing song is viewable via the mobile devices that thelogged-in registered users used to execute their respective loginoperations.
 9. The system of claim 1, wherein the memory comprisesfurther instructions that, when executed by the at least one processor,cause the at least one processor to at least limit the number of votes alogged-in registered user can place on any given song in the portion ofthe queue.
 10. The system of claim 1, wherein playlists of songs knownto be liked by logged-in registered users making selections are favoritesongs of the respective logged-in registered users.
 11. The system ofclaim 1, wherein the plurality of predefined playlists further comprisesat least one playlist including songs popular across a network ofout-of-home pay-for-play establishments.
 12. The system of claim 1,wherein the plurality of predefined playlists further comprisesplaylists for different genres and/or themes.
 13. The system of claim 1,wherein the plurality of predefined playlists further comprises at leastone playlist imported from an external source.
 14. The system of claim1, wherein the plurality of predefined playlists further comprises atleast one playlist imported from a music-related social networking site.15. The system of claim 1, wherein the predefined playlists are playablein whole or in part.
 16. A system operable to facilitate the playback ofmusic from a catalog of playable songs in an out-of-home pay-for-playestablishment, the system comprising a plurality of electronic device,each said electronic device comprising: at least one processor; and amemory coupled to the at least one processor, the memory comprisinginstructions that, when executed by the at least one processor, causethe at least one processor to at least: enable users to execute loginoperations to indicate that the users are present at the out-of-homepay-for-play establishment; in response to a logged-in user selecting asong, add the selected song to a list of songs to be played back at theout-of-home pay-for-play establishment; facilitate the playback of songsfrom the list in the out-of-home pay-for-play establishment; and enablelogged-in users to vote on at least some of the songs in the list;wherein: a user interface provided to portable electronic devicesoperated by respective logged-in users at the out-of-home pay-for-playestablishment is arranged to display (a) at least a portion of thecatalog of playable songs, (b) at least a portion of the list, (c)tallied votes made with respect to at least those songs in the portionof the list, and (d) an indication of a song currently playing at theout-of-home pay-for-play establishment; and the user interface isfurther arranged to enable songs to be selected from a plurality ofpredefined playlists accessible to users, the predefined playlistsincluding at least three of the following types of playlists: a playlistgenerated by a registered user, a playlist of songs popular at theout-of-home pay-for-play establishment, a playlist of songs known to beliked by a logged-in registered user making a selection, a playlist ofsongs popular across a network of out-of-home pay-for-playestablishments, a genre and/or theme playlist, a playlist imported froman external source, and a playlist imported from a music-related socialnetworking site.
 17. The system of claim 16, wherein each saidpredefined playlist has an associated playlist identifier thatidentifies the respective predefined playlist.
 18. The system of claim17, wherein the playlist identifiers include playlist names.
 19. Thesystem of claim 16, wherein the tallied votes include tallied counts ofvotes for, and separate tallied counts of votes against, each song thathas been voted on.
 20. The system of claim 16, wherein playlists ofsongs known to be liked by logged-in registered users making selectionsare favorite songs of the respective logged-in registered users.